Azure DevOps Services and Server

Currently when you import from Jira or Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in...

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

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

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...

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

What is the challenge? Each time I review Integration Updates I have to manually select the Workspaces, Integrations, and Record Types in varying levels to see the items needing to be addressed. Once I close out, and go back in later, I have to ...

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

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

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

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.