Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Linking Epics to higher level hierarchies

Hi All.

I wanted to start using Advanced Roadmaps for a project I inherited.

Using temporary full admin permissions I no longer have, I created Initiative and Theme issue types for the project scheme. Like this;


Theres a lot of extras in this scheme that I dont want to use, my objectives for this project are to have a hierarchy like;

Story / Task

I can give Initiatives a parent Theme;

Assign Initiative Parent.png

However, I cannot give Epics an Initiatives parents, or any parent really...;

Assign Epic Parent.png


What am I doing wrong here?

2 answers


There is an answer here:

Basically you will have to add "Parent link" field to your EPIC issue type screen. Then you will set up INITIATIVE as parent to EPIC. Last step will be to configure roadmap hierarchy under: Plans->Administration->Hierarchy configuration

When completed you will be able to set up parent issue to EPIC's on roadmap plan.


You're right about the use of the Parent link. It must be done so that Jira knows that Initiative to link the Epic to.

Like # people like this

Thank you Tomasz and Ric both. Through checking your advice, I think I'd found my problem. A strange issue type that exists in between Epic and Initiative, that I cant skip, even though that strange issue type is not available in my project...

So I'd already performed that step of adding a Parent Link field, but it still wouldnt let me connect an epic to an initiative;


So when I click the down chevron, I see a list of issues of a type that was created in a trial performed by another team I have no contact with;


and I cant skip that issue type in the hierarchy even though it is not part of my project.... argh....


So the existence of this "Requirement(Jama)" issue type somewhere in my large organization, which is not even in use by my project, is preventing me from using advanced roadmaps in a way I want to.

Does anyone know of any way to get around this without breaking what the other team are doing with this issue type??


Thank you!

If I recall correctly, I had to include a filter, in my list of Issue sources, that includes the list of Initiatives and Themes I want my epics linked to.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events