Azure DevOps Services and Server
Sort by:
Trending
Status:
Showing 120
4
VOTE
Allow two-way integration for picklist fields in Azure DevOps when using the XML process model
This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
0
Future consideration
5
VOTE
Ability to customize the Import Import New Records dialog box and functionality
It would be very helpful to be able to customize and configure the Import New Records dialog box. Specifically I would like to be able to select additional/different information about each record (i.e. Azure DevOps work item #, State, Iteration) i...
0
Future consideration
2
VOTE
Include author of comment from Azure DevOps when saving to Aha
We use the Aha <-> Azure DevOps integration. Comments from Aha include the author when synced to AzDO (Comment added by <user> in Aha! - View). The reverse is not true. Comments made in AzDO that come to Aha do not say the other, just ...
0
Future consideration
4
VOTE
Allow Integration variable on Create Record layout
Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
0
Future consideration
2
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
1
Future consideration
1
VOTE
Text from Azure DevOps into custom fields shows with HTML elements
What is the challenge? When syncing a "text" custom field with Azure DevOps it shows the text with HTML elements What is the impact? It makes the custom field text difficult to read Describe your idea Ensure text custom fields convert HTML tags wh...
0
Future consideration
2
VOTE
Aha! Releases Should Honor ADO Area by Default
I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
0
Future consideration
4
VOTE
Azure DevOps integration support for designating default Iteration as backlog
Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
2
Future consideration
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
1
VOTE
DevOps Integration: button to receive all fields
What is the challenge? Possibility to easily refresh an item from DevOps What is the impact? In case of non-synchronized items, it will be easier to refresh the status from DevOps Describe your idea Currently, when an item is linked to a correspon...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved