Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 121

Add ability to restrict auto import of parent record with ADO

What is the challenge? When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha! What is the impact? Difficulty in ...
Kristina Gass about 10 hours ago in Azure DevOps Services and Server 0

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

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 7 months ago in Azure DevOps Services and Server 1 Likely 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 6 months ago in Azure DevOps Services and Server 2 Future consideration

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

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

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 3 months ago in Azure DevOps Services and Server 0 Planning to implement

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 6 months 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

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