My ideas: Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 118
3
VOTE
Show name of user whose token is being used in ADO integration
Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
0
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
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
7
VOTE
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 Area Company/Functional Area/Team The Aha Azure devops integrat...
5
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
Allow mapping fields from related records in Aha to Azure Devops
This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
0
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
3
VOTE
Function as a hub to push data from JIRA to DevOps
We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved