You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
This question is in reference to Atlassian Documentation: Configuring initiatives and other hierarchy levels
I'd like to create the following hierarchy levels:
However, I don't know how to change the default hierarchy:
I can create an Initiative above Epic, but I cannot introduce a Task between Story and Sub-Task.
How can I adapt the default hierarchy to the 5 levels specified above? Is it possible at all? If nont what would you suggest to get those 5 levels?
Stef
JIRA does not have a changeable hierarchy.
JIRA Core allows for Project, Issue/Story, Sub-task. (You could argue that Category groups projects and you can use components to break down issues within a project into other groups, but I don't see those as hierarchical)
JIRA Software adds Epics to that, converting the issue type to behave as a container for stories and issues.
JIRA Portfolio adds Initiatives.
And that's it really. You can't wedge other layers in, it's simply not supported, as the hierarchy is hard coded.
If you're on Server versions, you could add the Structure add-on, as that plays some tricks that makes it look like there are more layers within the Project/Story/Subtask framework, and it does it reliably and clearly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.