Azure DevOps Services and Server

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...

What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...

What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...

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...

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...

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