Issue type hierarchy

[Olaf Kleine Hörstkamp]

I set up Issues; Initiative, Epics, Stories, tasks and Subtasks. 

In the section Issue Type Hierarchy I can't set up the hierarchie. E.g. on the first Issue "Initiative" I only can set up "Initiative" AND "Epic", not stand alone "Initiative". Because of this first setting, I can't set up the following Issues....

Anybody for help please?

Best 

Olaf 

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Are you using Advanced plans to do this?

If so, you've created a bit of a problem for yourself, because you've put Stories at the Epic level.  This assumes I am reading it right, you have given us the five layers you want to use?

[Olaf Kleine Hörstkamp]

Nic, many thanks!  Yes I'm using advanced Roadmap, but I tried everyting to change the hierarchy! 

I Cant get

• Initiative to the first level
• Epics to the second
• Stories to the third

level, because I can't drag and drop the levels after entering the fields at the "Issue hierarchie" screen .

And sometimes I can't only enter in "Jira Issue types" "Initiative" to the "Initiative" Level. Thats only possibe when I put the Initiative to level three, but it should be level 1, or??

Many many Thanks!

Best Olaf

[Nic Brough -Adaptavist-]

Ok, most people would want to use stories on the base level, not the Epic level.

Let me run over how Jira's hierarchy works.   If you look at a mostly unaltered hierarchy in a sample Jira, you're likely to see something like:

#	Level Name	Issue types
3	Initiative	Initiative
2	Feature	Feature
1	Epic	Epic, Book
	Story	Issue, Story, Bug
	Sub-task	Sub-task, Technical task

(This one has been altered slightly - "Book" has been added to the default Epic level)

The structure for 1 downwards is fixed in Jira, you cannot change it.

All you can do in this hierarchy is swap 2 and 3, but you could add 4, 5 etc above 3.

You can also rearrange your issue types into any level you want, as long as they are standard issue types (i.e. not sub-task types, or the default epic)

If, for example, I wanted "Book" to be at the Feature level, I would have to remove it from the Epic level, and then add it to the Feature level.

[HIMANSHU KUMAR]

I have also got requirement of 5-level hierarchy. I have did little customization which fulfill the all projects requirements.

In my Org, I have also customize the hierarchy level as per the requirement as our org is following waterfall method. So, I have used "Project Details", "Milestone" and I have disabled the epic issue type. On Epic level I have used "Story", "Bug", "Defect".

So, hierarchy level would be: Project Details ->Milestone -> Story/Bug/Defect ->Task->Sub-task.

#  Level Name                 Issue types 
 3  Project Details            Project Details
 2  Milestone                   Milestone
 1  Epic                            Story, Bug, Defect
   Story  
   Sub-task                       Sub-task

[Nic Brough -Adaptavist-]

That's probably not a good idea - you no longer have a base-level issue, so all your stories, bugs, and defects are now all cross-(jira)-project epics.

[HIMANSHU KUMAR]

I understand your concern but we are not using Agile methodology, So we are not using epic in our project. But instead of epic we are using custom hierarchy that's why we are using Story, Bug, Defect at epic level. We need to define naming nomenclature and hierarchy as per waterfall method only.

[Nic Brough -Adaptavist-]

Um, none of this is about agile, it's all about the hierarchy, whatever your process structure is.