Azure DevOps Services and Server
Sort by:
Popular
Status:
Showing 109
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
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
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
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
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
Ability to refresh data from the development tool for a single Aha record
Sometimes I'd just like to fix a record or two that have gotten out of sync. When I click on the Integrations menu for a particular feature, I have the option to resend all fields to my development tool (Aha -> ADO), or, to delete the link. IDE...
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
© 2025 Aha! Labs Inc.•All rights reserved