Azure DevOps Services and Server
Sort by:
Trending
Status:
Showing 120
9
VOTE
Adjust ADO integration behavior for records that are linked across workspaces
What is the challenge?
Integrations have been setup using an integration template and they are associated to multiple workspaces.
When a feature is created in workspace 1 and connected to an epic in workspace 2 an error is received when the fea...
0
Planning to implement
1
VOTE
Receive an email notification when something is in the "integration updates" tab ready to import
What is the challenge?
As we do not use releases for some workspaces not everything pulls in automatically, so there are things in the integration updates tab that we don't know are there until we check it.
What is the impact?
Sometimes we...
0
Future consideration
14
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...
1
Likely to implement
10
VOTE
Fix date syncing between Aha! and ADO
What is the challenge? Dates added on AHA/ADO are not properly synced and show up on the other tool as +/- 1 day as a result of time differences between the two tools. Expected behaviour: When selecting a date in one tool, the same date appears in...
2
Future consideration
28
VOTE
Azure DevOps Integration - Sync dependencies at UserStories/Requirements level
What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
0
Future consideration
4
VOTE
7
VOTE
Support ADO deployment controls syncing to Aha!
What is the challenge? ADO has released the ability to visualize deployment controls within an ADO record. In order to share this information with product management, this information needs to be able to sync back to Aha! via the ADO integration. ...
0
Future consideration
24
VOTE
Support AzureDevOps "work item deleted" events so my Aha records aren't out of date
Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...
0
Future consideration
4
VOTE
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...
0
Future consideration
13
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
© 2025 Aha! Labs Inc.•All rights reserved