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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,466,623
Community Members
 
Community Events
176
Community Groups

Customised hierarchy

This question is in reference to Atlassian Documentation: Configuring initiatives and other hierarchy levels

I'd like to create the following hierarchy levels:

  1. Initiative (a big strategic topic, covers typically several projets)
    1. Epic (typically a big project)
      1. Story (a part of that project, mostly a specific stage of the projet)
        1. Task (Task within a story or project stage)
          1. Sub-Task (Classical sub-task of a bigger task)

However, I don't know how to change the default hierarchy: 

  1. Epic
    1. Story
      1. Sub-Task

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

1 answer

1 accepted

0 votes
Answer accepted

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.

Thanks Nic, short and clear. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events