Azure DevOps Services and Server
Sort by:
Popular
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
4
VOTE
Ability to search for key words in Integration updates when importing new records
After the updated TFS integration which allows records to be imported directly from TFS into Aha. It would be ideal to be able to search the new record list for key words. Currently you can filter the list but this is not very user friendly and if...
1
Future consideration
3
VOTE
Support syncing of editing existing comments via ADO
What is the challenge? Editing existing comments in ADO do not sync back correctly in Aha! What is the impact? Comments can become out of date and not contain the correct information. Describe your idea Sync edits to existing comments
0
Future consideration
3
VOTE
Add ability to map Created by Field between Aha! and ADO Server accounts
What is the challenge? Currently there are a few user fields from ADO server accounts available to map to Aha!'s Created by User, but the Created By user is not displaying as an option. What is the impact? Users are unable to map the created by fi...
0
Future consideration
3
VOTE
Allow use of Mapped fields template with one field difference for each integration
What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
0
Future consideration
3
VOTE
Show name of user whose token is being used in ADO integration
Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
0
Future consideration
3
VOTE
Function as a hub to push data from JIRA to DevOps
We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
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
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
© 2025 Aha! Labs Inc.•All rights reserved