Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

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 over 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

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 almost 4 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 about 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 Master F...
Guest about 5 years ago in Azure DevOps Services and Server 2 Future consideration

Calculate remaining effort based on detailed estimate and work done

What is the challenge? When adding a detailed estimate in Aha! or ADO and then logging actual effort via ADO, the Actual effort remaining value does not change and the progress bar total is inaccurate. Add initial estimate in aha! Send to ADO. Add...
Stuart Blair 7 months ago in Azure DevOps Services and Server 2 Future consideration

Support AzureDevOps "work item deleted" events so my Aha records aren't out of date

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...
David I. 9 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 Dev...
Guest almost 5 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 over 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 about 9 years ago in Azure DevOps Services and Server 1 Unlikely to implement