Possibility to link an EPIC to two different parents in Advanced roadmap?

[Lars Stenlind]

When using Advanced roadmap the tree-view for Initiative-EPIC-Task is really great. The problem occurs when a Project want to link-in EPICs from contributing teams to an Initiative, but the Teams wants to group their EPICs under something in their own Jira project as well. I've read that you can not link an EPIC to more then one Initiative, but can you create another issue-type and link EPICs to that one, while still linking EPICs to an Initiative?

[Fazila Ashraf]

Hi @Lars Stenlind 

Welcome to community!

Even if another issue/issue type is created , the parent field can hold only 1 value. 

For the other team, can they use the dependency link instead of setting the Epic as a parent to their own initiative?

[Lars Stenlind]

Hi Fazila,

Ok, yes so if only one parent regardless of type is possible to add then that will not work either then.

Sorry perhaps I'm missing something here, but is that not only to show blocking dependencies in Advanced roadmap, in the timeline part? That does not give the team the possibility to group EPICs in a tree-view, right?

I know we can group them under components as well but it would have been nice to not have to create a separate group for each component in Advancaed roadmap, and to tag all Task with it as well to have them showing up in the tree-view.

[Fazila Ashraf]

Right, it will be only to highlight dependency and doesnt work as the tree view. 

AFAIK what is used is not possible in plans/roadmaps but should be possible if you are using other commercial plugins for project planning. Like Structure

[Lars Stenlind]

Ok, I'll have a look at Structure

Thanks!