Would be a great addition to my organization because of different phases of products but can link to multiple epics. this is mainly for code development planning.

I would love for this feature to be added, there's no point adding complex "systems engineering" style issue types in a "Premium" subscription unless we can add multiple parents.

It's obvious that a Business Goal can be satisfied by multiple Business Requirements that much is already in the Jira software, but a Business Requirement can satisfy multiple Business Goals, and that ability is completely missing from Jira.  The same applies to User Stories and Epics, throughout the entire hierarchy really.

I feel like this was a "we can't trust the users" situation, but its a roadblock for developing more complex systems with Jira as a planning and tracking tool.

Is there an equivalent issue for this feature request for Jira Cloud?

Hi,

I really really like the idea of Advanced Roadmaps being able to not only show parent/child but to be able to tell the plan what links to display in the Gantt chart view.

How can we upvote this proposal, we are a large user of Jira in our organization.

BR

Johan

In the context of epics and initiatives, it seems logical to me to be able to link an epic to multiple initiatives. For us, epics tend to speak toward large feature or feature set developments. Those epics can often support multiple initiatives, for example, we may have one initiative to "reduce operational support" and another to "attract new clients", and then an epic to implement a feature that speaks meaningfully to both.

Seeing how a given epic impacts multiple initiatives helps to gauge the impact of that epic, and helps keep the watchers of that initiative informed on developments.

+1

I run a hierarchy up to the organization's Vision.

A strategy will often bubble up to affect multiple higher-level issues.

This is a fundamental requirement for a truly "advanced" roadmap.

This is still a valid requirement. Can Atlassian provide an update please?  

Splitting an Epic into 2 means the people doing the work then have to duplicate reporting and keep the two Epics in sync which is a waste of time and prone to error.

Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC

This may be a different model of how Initiatives and Epics work (to @Matt Doar's point), however since Advanced Roadmaps allows the creation of new issue types at the same level as Epic for something that might not necessarily be a traditional Epic (like a Milestone or Risk), there should be a way to allow specifying multiple parent relationships using the Parent Link.

Hello, I'd like to know if this is something that is even being considered by Atlassian as an update for Jira? It may be fundamentally different to how it works today, but it's still very necessary. So often a chunk of work is needed to accomplish multiple larger initiatives. And often those initiatives are owned by different teams. It's important to reflect that work in both roadmaps. I'm really stuck and looking for other tools to handle this since Jira falls so far short in this area.