Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 117

Support ADO multi-select dropdown

What is the challenge? Syncing multiple values between ADO <>Aha! requires support for the Multivalue control extension to work. Syncing editable choice lists works, pre-defined lists only sync 1 value when 2 or more are selected. What...
Tyler Carter 6 days ago in Azure DevOps Services and Server 0 Planning to implement

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...
Terence Osmeña 29 days ago in Azure DevOps Services and Server 0 Future consideration

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...
Guest 3 months ago in Azure DevOps Services and Server 2 Future consideration

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. ...
Bonnie Trei 3 months ago in Azure DevOps Services and Server 0 Future consideration

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...
Guest 14 days ago in Azure DevOps Services and Server 0 Future consideration

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...
Stephanie Lechner 4 months ago in Azure DevOps Services and Server 1 Likely to implement

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...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration

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...
David I. over 1 year ago in Azure DevOps Services and Server 0 Future consideration

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...
Ryan Bradley 28 days ago in Azure DevOps Services and Server 0 Future consideration

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...
Rob Stebbens 11 months ago in Azure DevOps Services and Server 1 Future consideration