ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 95

Support linking the Aha! URL field to the Azure DevOps Hyperlink field

Goal: We want to see in DevOps which Item it syncs with in Aha!Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single f...
Euan Callow 28 days ago in Azure DevOps Services and Server 1 Future consideration

Dependency record links available as part of the Azure DevOps integration

I understand you've created the dependency link in Aha! with Jira, it would be great to have this in ADO (Azure DevOps) too please
Ben Snapper about 1 year ago in Azure DevOps Services and Server 10 Future consideration

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 9 months ago in Azure DevOps Services and Server 0 Future consideration
111 VOTE

Ability to link features/requirements to existing VSO work items

Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful
Guest almost 6 years ago in Azure DevOps Services and Server 23 Shipped

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 over 1 year ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 1 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 over 3 years ago in Azure DevOps Services and Server 9 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 over 2 years ago in Azure DevOps Services and Server 7 Future consideration

Allow mapping Release as a field on Requirements in Azure DevOps integration

Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
Guest 29 days ago in Azure DevOps Services and Server 0 Future consideration

Allow to sync tags into VSTS

It should be possible to sync the tags into Visual Studio Team-Services.
Dirk Eisenberg about 5 years ago in Azure DevOps Services and Server 6 Shipped

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 over 2 years ago in Azure DevOps Services and Server 8 Future consideration