Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 92
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
1
VOTE
Exportable list of orphaned workitems in Integrations update modal
Who would benefit? Aha admins, dev lead What impact would it make? Improved collaboration, minimizing integrations admin How should it work? Use case: I want to inform and support development team creating Azure Devops work items on Requirement le...
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
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
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
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
0
Future consideration
4
VOTE
Import of time tracker data from 7pace Timetracker to Aha!
7pace timetracker is an integrated time mamagement solution for teams using DevOps. We would like to pull time tracker data into Aha! through our DevOps integration to ensure Aha! has a clear view of the time spent on Features.
1
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
3
VOTE
Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO
Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved