Azure DevOps Services and Server
Sort by:
Trending
Status:
Unlikely to implement
Showing 107
1
VOTE
Handle multi-select fields in ADO integration
What is the challenge? Running into an issue where multi-select from Aha can't flow over to ADO multi-select field. Only first value flows over from Aha. What is the impact? Can't use multi-select field in ADO properly. Describe your idea Allow fo...
0
Future consideration
28
VOTE
26
VOTE
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
0
Future consideration
2
VOTE
Enable tags to be a selection for Azure DevOps integration of requirements
What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
0
Future consideration
1
VOTE
Option to enable "bypassRules" for Azure DevOps integrations
What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
0
Future consideration
14
VOTE
DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"
Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
1
Future consideration
21
VOTE
Fix critical Aha to VSTS Integration not syncing Feature Order
We are trying sync the Feature order from Aha to VSTS (never the other way around).
Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration.
The reason that it fails is because matching the Aha R...
2
Future consideration
14
VOTE
Sync releases for Azure DevOps integration
Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
0
Future consideration
17
VOTE
Include Area Path in VSTS Integration
I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
3
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
© 2024 Aha! Labs Inc.•All rights reserved