Azure DevOps Services and Server

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...

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

Currently the Azure DevOps Boards integration does not include the capability to share the rank order of items in a workspace which results in the items in the Azure Devops Boards workflow having a different ordering than the items in the Aha rele...

We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...

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

As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...

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

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...

This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...