Azure DevOps Services and Server
Sort by:
Recent
Status:
Unlikely to implement
Showing 117
2
VOTE
1
VOTE
Add Markdown support for ADO integration
What is the challenge?
Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text.
What is the impact?
Makes integra...
0
Future consideration
1
VOTE
Enable Roll-up Initiative link in the standard Azure DevOps Services integration
What is the challenge?
Unable to integrate multi-layered strategic initiatives from Aha to ADO
What is the impact?
Manual updates to keep information in sync, prone to errors. Question whether we will continue to utilize Aha or work direct...
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
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
9
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
4
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
9
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
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
© 2025 Aha! Labs Inc.•All rights reserved