Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 95
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
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
3
VOTE
Sync DevOps Commenter Name in Comment Sync
We are an outsourced product management company, so we have alot of integrations to alot of our customers. We have found that when an individual in one of our customers orgs makes a comment, the comment text is sync'd, but the name of the person w...
0
Future consideration
3
VOTE
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
5
VOTE
Add ability to transfer requirements between features and features between master features (epics)
If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's).
However we are...
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
3
VOTE
Add ability to sync custom table one to many field with AZURE DevOps Fields
I would like to be able to sync a one to many custom field, that links ties to a custom table, we have added to our requirements (PBIs), with the iteration path from DevOps. This does not appear to be possible. The reason for this is that we have ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved