My ideas: Azure DevOps Services and Server
Sort by:
Popular
Filter by:
Status
Showing 104 of 8836
9
VOTE
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...
0
Future consideration
8
VOTE
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...
0
Future consideration
8
VOTE
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 ...
2
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
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
7
VOTE
Nested Iteration Paths with VSO / Visual studio team services integration
We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path.
Our...
0
Already exists
6
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
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
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