Jira Premium hierarchy

BenWade

I need this hierarchy. How to achieve it?

0 Project A -> 1 Theme-> 2 Initiative -> 3 Epic-> 4 Story-> 5 Feature -> 6 Subtask.

So basically I have to shift my hierarchy one level up. But I cannot do it. I cannot drag 2 below epic. 

this is why I am thinking to rename levels. Like this:

But I do not risk to press "Save Chnages" I have several projects and around 700 issues. I am afraid it can break the current structure, cause issues. This is why, I am asking you what should I do in this case? 

I am also thinking that if I rename my epic, then it will impact the timeline view. But since I have plans in Jira premium, the timeline can be kind of replaced by Plans. This is my initial thoughts. 

The main thing is that I need this hierarchy and have to find a way to create it properly.
what do you think? Is my approach viable and if I press save chnages will this break the current configurations, worklow, etc?

Trudy P Claspill

@BenWade 

My experience with the extended issue hierarchy is limited so I hope somebody else chimes in.

If you rename the hierarchy levels, that does not impact the actual Issue Types that can be used at each of those levels. I don't actually know where the level names are used besides in this screen.

The issue types that are used at each level are specified in the column to the right. Notice that still shows the Epic issue type in the level you have named "Story".

And the level you have named "Feature" says "all other standard issue types". That means any issue type not show at a higher level in the hierarchy can be used at the Feature level. The Story issue type would still be a child of an Epic issue type. 

And since issues at the same level cannot be made children of each other, the issue type you create and name "Feature" could not be a child of and Story issue type, as they would both be "all other standard issue types.

To build the hierarchy you want based on issue types you would need to change the issue types shown in the right side next to each level.

You would have to add the Story issue type to the level labeled "1".

• Or rename your existing Epic issue type to Story. 

You would have to move the Epic issue type up to level "2".

• If you are following the "Or..." path, you would need a new issue type that you named "Epic" and add that to level 2.

 

However, this hierarchy is a global setting, and it would affect all your projects.

Also, renaming the existing Epic issue type to something else can impact third party apps that added functionality specific to Epics. And changing the names of issue types affects all existing issue that use that issue type.

 

Before making any such change I encourage you to create a sandbox from your Jira instance, copy the production data to the sandbox, and try out the changes there to see the impact.

https://support.atlassian.com/organization-administration/docs/manage-product-sandboxes/