Skip to Main Content
Status Future consideration
Created by John M
Created on Aug 3, 2020

Inherit the hierarchy of the area paths from Azure Dev Ops

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 integration only allows integration to a single area path per integration.

As a result. we have had to set up 18 different integrations in order to get all of our work items in to Aha and some of the linkage between work items which exists in Azure Dev Ops is not present in Aha.

  • Attach files
  • Admin
    Julie Price
    Aug 5, 2020

    I apologize as I misunderstood.

    Currently, the Jira integration allows you to have an epic in Project A and child stories in Project B, and we keep the parent child relationship intact if you have two integrations using the same template.

    I believe the solution in this idea would give you what you need once it is prioritized: https://big.ideas.aha.io/ideas/AFPR-I-7671

    Does that feel more aligned to what you need?

  • John M
    Aug 5, 2020

    Hi Julie, dont you support the equivalent relationship between work items for Jira integrations though? So is the data model really a limiting factor for this?

  • Admin
    Julie Price
    Aug 5, 2020

    Thank you for clarifying! Your use case does make sense.

    Currently, integrations are configured at a product level in Aha! so this is not possible with our data model.

    However, we will continue to monitor this idea for community feedback.

  • John M
    Aug 5, 2020

    Hi Julie, we are trying to represent work items that sit across multiple area paths in Dev Ops in Aha.

    One of the issues that we are facing is that if we have an Initiative sitting in one area path and a number of linked Epics and Features across multiple different area paths then that relationship is not mapping across to Aha.

    Aha seems to treat each area path in Dev Ops as stand alone rather than recognising the hierarchy.

    Does that make sense?

  • Admin
    Julie Price
    Aug 4, 2020

    Thank you for the idea!

    Today, you can map the Area Path value to an Aha! field in your Aha! integration - mapping tab, adding visibility into where the record lives.

    Curious, are you trying to send records from 1 Aha! integration to multiple different Azure area paths?