Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 118 of 9560

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 about 1 month ago in Azure DevOps Services and Server 0 Planning to implement

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 4 months ago in Azure DevOps Services and Server 2 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 6 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

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 2 months ago in Azure DevOps Services and Server 0 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 4 months ago in Azure DevOps Services and Server 0 Future consideration

When Sending Whiteboards to Integrated Devops, Send as image, not link

What is the challenge? When a Whiteboard is included within a feature that is sent to DevOps (and I assume Jira), a link is sent, not an image. What is the impact? Many, if not all users in DevOps do not get access to Aha Describe your...
Guest 19 days 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...
Guest over 1 year 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...
Guest about 1 year ago in Azure DevOps Services and Server 1 Future consideration

Calculate remaining effort based on detailed estimate and work done

What is the challenge? When adding a detailed estimate in Aha! or ADO and then logging actual effort via ADO, the Actual effort remaining value does not change and the progress bar total is inaccurate. Add initial estimate in aha! Send to ADO. Add...
Stuart Blair over 1 year ago in Azure DevOps Services and Server 2 Future consideration