Issue Hierarchy: Can't alter #1 and #2

[Kate Madden]

I created a new issue type, Initiative, that will be above Epics. I created the issue type but can't drag it above Epic. Epic continues to stay at #1.

[Joseph Chung Yin · Accepted solution]

@Kate Madden -

Welcome to the community.  To supplement what @Fabian Lim mentioned.  This is what you should see (NOTE - this is assuming that you have the system admin rights) 

When you create a new hierarchy level it will always be placed above Epic (#1) level.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Yuta Nagano]

Hi @Joseph Chung Yin , do you know how to take Initiative from #2 to #1? I still can't get my initiative to pull up on the roadmap

[Joseph Chung Yin]

@Yuta Nagano -

Welcome to the community.  Can you send a screenshot of your Hierarchy setup screen?  What is the issue type listed above Epic?

Best, Joseph

[Yuta Nagano]

Thank you for the welcome, @Joseph Chung Yin ! Here is a screenshot of the task hierarchy above. When I created the new level/issue type it automatically labeled it as #2. This is immutable and cannot change for some reason. Is there a way around this?

Additionally, Initiative pops up as an option on the "+ create issue" button in Plans, but is greyed out. Not sure why it isn't clickable even though the new project I created has initiative as an issue type.

[Joseph Chung Yin]

@Yuta Nagano -

Unfortunately, you cannot switch the ordering since EPIC (special issue type) is system default and any hierarchy setup on adding new issue type will always be above EPIC.  The numbering sequencing will just go upward (i.e. Initiative is a parent of Epic, thus it will be labeled as #2).  However, anything above EPICs you can change the ordering.

On your other question of Initiative being grayed out when you try to create issue in the plan, it is because the view filter on the view that you are using didn't set Initiative in the "Hierarchy" option.  So you just need to adjust it to include it.

Hope this helps.  If it helped you, please click on Accept answer when you have a chance.

Best, Joseph

[Yuta Nagano]

@Joseph Chung Yin Thank you so much you are such a life saver!!

[Joseph Chung Yin]

@Yuta Nagano -

You are welcome.  Please click on "Accept answer"  when you have a chance, so others with similar question will see this case as a solution.

Best, Joseph

[Joseph Chung Yin]

@Yuta Nagano -

If my assistance helped you, please click on "Accept answer"  when you have a chance, so others with similar question will see this case as a solution.

Best, Joseph

[Yuta Nagano]

@Joseph Chung Yin I'm not sure how to do so... I see the 3 dots next to your posts, but when I click it the only option is to report the comment. I don't see where I can accept the answer.

[Fabian Lim]

Hi @Kate Madden

Welcome to the community!

Have you worked with your sys admin to update the hierarchy? Look at step 3.

Link:https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

[Danno]

One more thing to look for. Be sure you have the parent link field available in your Epics to be able to link them to the Initiative that is the Parent.