RELATED IDEAS
Support parent-child moving across workspaces and Jira projects
In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration does not currently support maintaining the parent-child linkage.
It's not feasible to manually link the parents to their children in each system as it causes too much potential for error.
-
ADMIN RESPONSEDec 5, 2024
We have improved our Jira and ADO integrations to support many to many scenarios;
Moving records
Linking parents
Single workspace > Multiple Jira projects
Supported
Supported
Multiple workspaces > Single Jira project
Supported
Supported
Multiple workspaces > Multiple projects
Not supported
New
Supported
It's worth noting that we allow this to cross-project linking to happen even if the integrations do not use the same template.
© 2024 Aha! Labs Inc.•All rights reserved
This functionality is foundational in competitive tools such as (JIRA Align). It does not have to be a limitless many|many relationship as often you will not experience more than 7 teams working on the same body of work. The lack of this integration limits the usefulness of road mapping reporting in highly collaborative environments.
This is critical for us. Not supporting this is requiring us to look at keeping less data in Aha and using Jira independently more.
Hi Kelly! That's right, this is for a many to many setup.
Hi Michael! There are some scenarios where the integration supports maintaining parent-child links across workspaces and projects, but one where it cannot currently.
Supported
Single Aha! workspace > Multiple Jira projects
Multiple Aha! workspaces > Single Jira project
Not supported
Multiple Aha! workspaces > Multiple Jira projects
Does your scenario fall into that last category?