Adjust Jira Issue Type Hierarchy so that you can change the level of Epic

[James Woyciesjes]

Jira Issue Type Hierarchy

We are running SAFe Agile and use the following hierarchy:

(Initiative/Objective/Project) > Epic > Feature > Story > (Task/Sub-task) hierarchy.

We would like the function of a level 1 for the Feature in the Scrum board backlog. 

In Jira Cloud, we are not able to adjust the level of the Epic as it is greyed out.

The current workaround that gets us partially there is to create a new version of an Epic called SAFe Epic and then either move Feature to a level 1 or create a second iteration of a feature issue type.

[Bharat Kalia · Accepted solution]

Hello @James Woyciesjes - I was going through the documentation here and it seems like  by default Epic issue type will be associated with the Epic hierarchy level (level 1). You can add additional Jira issue types to associate them with the EPIC level but cannot actually remove the EPIC issue type from that level. 

You workaround is correct as well but if you want you can also rename the default "EPIC" and create another one at a different level - - however, this wouldn't change the built-in semantics in Jira for example if you renamed EPIC to XYZ , XYZ will be still treated as epic in boards but what you'd call EPIC would not be treated as epic. 

Thanks,

Bharat

[James Woyciesjes]

Thank you for the XYZ comment. I hadn't thought of renaming the native EPIC. That would be a potential solution. Thanks!