Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 103

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest almost 6 years ago in Azure DevOps Services and Server 3 Future consideration

Need full two way integration of a Story with VSTS

Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need: 1) any story delete in VSTS to be automatically deleted in Aha 2) any story added in VSTS to a Feature...
Eric Reichel almost 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze over 3 years ago in Azure DevOps Services and Server 1 Future consideration

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Ronnie Merkel almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

Allow additional Link Types in the 'Links to' field

Within AHA we are mapping Releases -> ADO Release Work Item Master Feature -> ADO Epics Features -> ADO Features. Master Features need to be located in the Release in which they complete. But Features (that contribute to this M...
Guest over 4 years ago in Azure DevOps Services and Server 2 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 Dev...
Guest over 4 years ago in Azure DevOps Services and Server 3 Future consideration

Control how Estimates are converted and sent to TFS/VSTS

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
Guest about 6 years ago in Azure DevOps Services and Server 1 Future consideration

Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project

Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
Alex Bartlow over 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

Ability to set Aha field to a constant value as part of integration field mappings

My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
Tessa Adair over 5 years ago in Azure DevOps Services and Server 7 Future consideration

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 ...
Euan Callow almost 3 years ago in Azure DevOps Services and Server 2 Future consideration