Changing hierarchy level of "Spike" type

[Abhay Kulkarni]

Hello! 

I created a new issue type - "Spike", and when I try to add a parent to it I get the message - 

"The selected issue type is at the top of your issue type hierarchy and cannot have a parent". 

How can I change this? 

[Trudy Claspill]

Adding to what the others have said I want to call out a risk.

If you already have Spike type issues, and if they already have Child issue associated to them, then moving the Spike issue type to another level will remove the connections between all Spike issues types and their Child issues.

[John Funk]

Hi Abhay,

I would say just delete it in the Hierarchy and then add it back at the level you want. You can have multiple issue types at the same level - say at Level 1. 

[Marc - Devoteam]

HI @Abhay Kulkarni 

Then you need another issue type that is set higher in the hierarchy to be able to assign a parent to a Spike.

See this article on hierarchy in Jira ootb and in the document you will find a link to advanced roadmaps hierarchy (Plans)

https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/ 

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

[Florian Bonniec]

Hi @Abhay Kulkarni 

It's a global configuration so you need to be JIRA Administrator in order to do that. The kb below should help you to achieve whay you are looking for.

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

Regards