Azure DevOps Services and Server
Sort by:
Recent
Status:
Unlikely to implement
Showing 110
3
VOTE
Sending child records to one ADO project should not error out if parent record is integrated to a different Workspace and ADO project
What is the challenge? Users are now able to support linking work between multiple Aha! workspaces and multiple ADO projects with parent/child relationships spanning this; however one scenario is producing an error. When a parent record is integra...
0
Likely to implement
1
VOTE
Import items even if a parent is not available due to security restrictions
What is the challenge? Some of our work items (e.g. a feature) in ADO are linked to security related parents (e.g. an epic) in ADO. We are not able to access the parent work item due to these security settings. However we would like to see the fea...
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
2
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
4
VOTE
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
5
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
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
11
VOTE
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
1
Future consideration
1
VOTE
Support configuring capacity units of time for ADO server integrations
What is the challenge? Currently the "Configure" option to select units of time to send estimates to ADO is only avaiable on the ADO Services integration and is not available for users using the Server integrations. What is the impact? Users are u...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved