Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 121

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...
Carah C 9 months ago in Azure DevOps Services and Server 1 Future consideration

Support relinking integrated records at scale

What is the challenge? Integration links can be lost for a variety of reasons. For organizations with a large number of records, it is not realistic to manually relink or reimport their backlog when this happens. What is the impact? Suppor...
Kristina Gass 4 months ago in Azure DevOps Services and Server  / Jira 0 Future consideration

Add the sprint rank (order) of a PBI to the integrations so Aha has the order of PBIs in a Sprint (Iteration)

What is the challenge? I cannot create a report in Aha where I can sort the requirements (PBIs) by their ADO rank. What is the impact? Limits my ability to create recurring reporting informing stakeholders of sprint priorities and limits A...
Julianne Dunnuck 18 days ago in Azure DevOps Services and Server 0 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 almost 2 years 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. about 2 years ago in Azure DevOps Services and Server 0 Likely to implement

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

Update existing integration parent Epic when auto updating from child Feature

What is the challenge? Integration is setup to azure DevOps. When a child feature results in an auto. update in parent Epic, and the feature and Epic are in different azure DevOps integrated projects, a second Epic is created in the integrated a...
Howard Meyers about 2 months 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 12 months ago in Azure DevOps Services and Server 2 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 over 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 almost 2 years ago in Azure DevOps Services and Server 2 Future consideration