Add support for Jira "Parent Link" field

Hi there, you can now define a Links to relationship to initiatives in the Mappings step of your integration setup. If you have any additional questions while configuring this, please reach out to our Customer Success team at support@aha.io.

Since the status of this is now "shipped", is it available in production for us to use this and if so, how?

Would be great to have this implemented. Looks like it was raised on Oct 2019 and has not been implemented within 2 years. Do you have any timeline on when this will be delivered?

We have the exact same problem and it is extremely frustating.

I take it this will also cover the Epic/Initiative relationship when it's resolved.

Finally I see I'm not the only one spinning my wheels to figure out how to carry-over the parent mapping for the Jira integration with Aha. We also have a custom level (Capability) in Jira that is higher than Epic. The inability to ensure that when the Epic (from Jira) comes back to Aha linked properly to its parent (Capability in Aha that also exist in Jira) is a HUGE disappointment and pain-point for the user community.

Has there been any success in finding a work-around until Aha decides to "Ship" this idea??
How many more votes are needed before this is prioritized??

Is really important to us in order to maintain the initiative relationship in both Jira and Aha.

This is important for customers with the Portfolio add on.

I am implementing a hierarchy of goal > initiative > feature > requirements in Aha. I have mapped the Aha initiative > Jira (Portfolio Manager) initiative, feature > epic, and requirements > story, new feature, etc. Goals are only managed in Aha at this time.

The problem is that I don’t require every feature to be a part of an initiative. So, if I map the feature to be a child record of the initiative, any epic created by the development team in Jira will effectively be ignored because it won’t be able to be imported into Aha. This results in my release not being accurate in terms of work getting done. (I may also create a feature that isn’t part of an initiative in Aha or JIRA because it may not be big enough or doesn’t relate to bigger things going on).

This is a vital feature. To enable complete visibility across both Product and Engineering departments in their tools of choice. Also as the integration between the Initiative in Aha and an initiative issue type in Jira exists and works, it is not clear that the parent linkages would not be carried across too. For me this should be an obvious requirement for the initiative integration - it's child relationships should be created and maintained in Jira.

Agree with other comments. Linking Jira record types above Epic in the hierarchy to Aha (i.e. Initiatives) provides the higher-level view that product managers are looking for, while Jira Portfolio provides a better cascading granular view down to the story and task level to track incremental progress. This is especially relevant for Initiatives involving primarily backend work. Not sure I see the value of the Jira/Aha! integration without support at higher levels.

This is also important for customers who have transitioned to JIRA next-gen projects.

I believe this is a very important feature for customers that use Portfolio / programs for large applications.