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!


Customer hierarchy in Jira

Im looking for some tips on best practices for configuring Jira. My organization runs a pretty typical SAFe situation with business goals being broken down into Epics, these Epics get broken down into quarter(ish) sized features, and then dev teams create user stories to implement these features which are executed on a sprint cadence. 


I have Jira premium with Advanced Roadmaps and I'm trying to configure a customer Issue type hierarchy but I want to be able to display 

1) Quarterly plans at the Epic level

2) Increment plans at the feature level

3) sprint plans at the dev team story level


Will Advanced roadmaps allow me to keep that hierarchy in place and provide visibility into the status and dependencies at all levels? I want to make sure I configure this correctly out of the gate. 

2 answers

1 accepted

0 votes
Answer accepted
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Nov 10, 2023

Hi @Levi Clarke

the bottom 3 levels of the Advanced Roadmaps hierarchy are always Epic / Base issue types / sub-tasks. You can only add new hierarchy levels on top of that. What you can do though is to rename the epic type and level - but even then, the epic level will always have certain semantics, e.g. in the Backlog or Active Sprint view.

If you really want to mix additional levels into the bottom 3 levels - I wouldn't really recommend doing so - you can only do that via issue links. Jira itself won't recognise these issue links as parent/child relationships, but there are apps in the Atlassian Marketplace that can help with this. Happy to elaborate if this is something that might be of interest to you.



Thanks Hannes, I think the best thing for me to do is embrace the terminology and go with the tool. 


Initiative -> Epic -> Story. 


It'll take a while to get used to it but I think its the best way. 

In trying to configure this on my own I can't seem to move the "Epic" issue type to the top of the hierarchy. I can't "uncheck" it from the #1 level. See screen shot below:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events