Map Aha Initiative to JIRA Portfolio Initiative

Hello Chrissi,

As I understand, a Jira Initiative exists as an object in a Project, and it may have child links to issues (Epics, etc) that can be spread across that Project and other Projects. So conceptually an initiative can be multi-project, but its data object is held in one place.

Right now, the Aha!-Jira synchronisation allows us to connect the basic objects in their appropriate places - I have Integrations for each Jira Project, and I can use those in sequence to send the right Epics to the right Projects. I can then send the Initiative to the appropriate Project. Of course, the problem is I then have to manually update the Initiative-Epic links in Jira.

Thanks

Nick

Hi there. Thanks for sharing that about Jira initiatives. To clarify, do you mean that Jira initiatives themselves can span multiple projects? Or that the Jira initiative's child records (e.g. epics) can span multiple projects?

We are using Jira Portfolio and Aha! in conjunction. The ability to carry across Initiative-Epic links would be really useful. At the moment we can connect the initiatives themselves but the links have to be handled manually (with obvious risk of getting out of sync.)
I think I can appreciate the difficulty with implementing this: Jira Portfolio allows Initiatives to span multiple Projects, but the Aha!-Jira connection is made at the Project level. So handling the full set of data behind an initiative would be a multi-step task.
However, there is still a significant value in having this support, irrespective of the complexity of its implementation. I must admit, I'm not that sympathetic when my developers say "that's hard to do!", and I'm sure Aha! can find a way to do this work.

We have a contractor delivering a major initiative that works with SAFe, and they use Jira. With the current integration, we are not able to effectively utilize Aha to visualize and manage the work or the dependencies across other initiatives. Having this addressed would add a lot of flexibility for the teams while still reflecting all of their work in Aha.

Very surprised to see this request is 3 years old. The lack of the feature prevents adoption of large enterprise implementations. We need mappings and maintaining of relationships that were created in Aha to be reflected in Jira

Epic, Stories and Releases that are built in an Initiative in Aha should have those links maintained in Jira. Very disappointing.

To add to my comment, The Jira integration needs to include portfolio fields as well as standard and custom Jira field mapping and it needs to be part of the Jira integration and mapping and not a separate integration

This is a needed feature, and to add, the start and end dates are also needed for the integration

We would use this as well.

We would also take advantage of this capability

This would be a great feature to add. The Aha! to Jira link is too restrictive currently. 

Jira Portfolio now has an API! 
https://jira.atlassian.com/browse/JPOSERVER-438
Can that be used for the integration?