Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 86
5
VOTE
Update records selectively
The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
0
Future consideration
5
VOTE
Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps
Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...
0
Future consideration
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
Add warning text to Custom field Key field description that changing the key value will break integration
We found that changing the key-field string of a custom field will break existing integrations with ADO where the custom field is synced to an ADO field. There is no warning or anything. This is a big risk to us and to the trust that integration r...
0
Future consideration
2
VOTE
Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field
I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
0
Future consideration
2
VOTE
Text formatting when sending to Azure Boards
When sending work items Azure Boards, bulleted lists don't work properly in Azure. If I have a bulleted list in Aha, tabbing the bulleted list in Azure does not increase the level of the bullets. It just adds tabbed space between the text and the ...
0
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
2
VOTE
Allow scheduled update of all linked records for DevOps
As the service hooks from DevOps to Aha are seldomly failing, it often results in having some records not in sync in Aha. This can be solved by running an update of all the linked records from the Aha integration page, but this requires to be manu...
2
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
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