Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 94
5
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
1
VOTE
Handle multi-select fields in ADO integration
What is the challenge? Running into an issue where multi-select from Aha can't flow over to ADO multi-select field. Only first value flows over from Aha. What is the impact? Can't use multi-select field in ADO properly. Describe your idea Allow fo...
0
Future consideration
4
VOTE
Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
2
Future consideration
12
VOTE
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 ...
1
Future consideration
8
VOTE
Integration to Azure DevOps for teams capacity planning
We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
2
Future consideration
1
VOTE
Option to enable "bypassRules" for Azure DevOps integrations
What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
0
Future consideration
7
VOTE
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
2
Future consideration
5
VOTE
Sync Release Phase to Azure DevOps
We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
0
Future consideration
5
VOTE
Provide item ranking capability with Azure DevOps integration to Boards
Currently the Azure DevOps Boards integration does not include the capability to share the rank order of items in a workspace which results in the items in the Azure Devops Boards workflow having a different ordering than the items in the Aha rele...
0
Future consideration
2
VOTE
Warn user of integration on epic deletion
Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved