ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 45

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO.When yo...
Guest 2 months ago in Azure DevOps Services and Server 0 Future consideration

Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although...
Tom Beck almost 3 years ago in Azure DevOps Services and Server 9 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release.Now that this date is set manually, it should be possi...
Austin Merritt 10 months ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 0 Future consideration

Inherit the hierarchy of the area paths from Azure Dev Ops

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/Company /Functional AreaCompany/Functional Area/TeamThe Aha Azure devops integration...
Guest 6 months ago in Azure DevOps Services and Server 5 Future consideration

Configurable unit of time for Estimation field

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC in...
Guest almost 2 years ago in Azure DevOps Services and Server 4 Future consideration

DevOps Integration -- Support rendering of images embedded in description field

Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps...
Mike Maylone 6 months ago in Azure DevOps Services and Server 0 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair almost 2 years ago in Azure DevOps Services and Server 3 Future consideration

Update records selectively

The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
Guest about 2 months ago in Azure DevOps Services and Server 0 Future consideration

Allow Aha! user name to populate DevOps board user

When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in D...
John Doe about 1 year ago in Azure DevOps Services and Server 3 Future consideration

Add Automation Rule Action to Trigger Link/Send to ADO Integration

When a Release has been agreed on and finalised you want to send the items through to ADO for developers to start work on then based on a Release Status or individual Feature Status (or other criteria) to Send the Features through to ADO based on ...
Guest 5 months ago in Azure DevOps Services and Server 0 Future consideration