Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Parent link use

In Portfolio I was able to set Parent link on a story level view or any other issue type lower than Feature/Initiative. Now in advanced roadmaps that doesn't seem to be an option.

I have following hierarchy:



Story (task, bug, defect, ..)


I need to be able to assign story level issue type to the Initiative as well as an Epic to an Initiative both using Parent Link.
If an Initiative is something that multiple teams are working on, some might have small contribution (few stories) , some might have an Epic size amount of work.

How do i make this work.


1 answer

0 votes
Dave Atlassian Team Oct 27, 2020

Hi @Julia Hunter ,

Unfortunately it is not possible as you cannot skip hierarchy levels (i.e. you cannot connect a story directly to an initiative).

Your options are to either create an epic to "bridge" the stories or to just an epic and give it a smaller (although I appreciate that this comes with it's own problem as an epic will not be shown on the main backlog view but rather in the sidebar).



Can I skip an epic level in the hierarchy and just go from Initiative to Story(same level issue types:bug, defect, task) level?

Dave Atlassian Team Oct 27, 2020

If you mean in the hierarchy configuration itself, then sadly not. This is something of a historical remnant from the origins of Advanced Roadmaps (formerly Portfolio) and the way that epic were introduced into Jira.

The relationship between story level and epic is fixed (and you can't actually move the default epic issue type to another hierarchy level - although you can add additional issue types to that level).

The relationship between story and epic is the epic link, the additional hierarchy levels provided by Advanced Roadmaps are parent link.

You can rename the epic hierarchy level, but you cannot move the epic issue type. Alternatively you could create new levels above epic and just not use epic and below - but I'm not sure how well that would work in practice.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

174 views 1 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you