Adding one more Epic issue type

[Aleksandar Djokic]

Hi All,

I would like to add one more issue type as Epic. However message saying "Moving or changing hierarchy levels of issue types will break existing parent links in all company-managed projects in your site. This change can't be reversed." is bothering me a lot, I want to make sure that this action will not mess up other projects. So, my structure would like on a screenshot - default epic type will remain, I will add one more. Will that mess up hierarchy of the projects using default epic type?

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Like @Alex Koxaras _Relational_ says, I would always try this on another instance.  Unlike Alex, I have had the "luxury" of having tried it elsewhere.

The warning it gives you is very carefully constructed English and if it is read as intended, it does actually give you the right information.

"Moving or changing hierarchy levels of issue types will break existing parent links in all company-managed projects in your site. This change can't be reversed."

It is correct, if you change an existing level that is in use, it destroys the hierarchy that you've got on your issues, because there's no way it can't.  Your data has to take on the new shape. 

But it does not actually mention adding new issue types in a level.  Because that's a new part of your hierarchy, you aren't actually using it yet.  So, you can simply add the new issue type into the level and although it is a change of shape, nothing is using it, so there's no data to change or remove.

The instant you've created an issue of the new type and used it inside your hierarchy though, then you have to worry about the impacts of changing it.

[Aleksandar Djokic]

Thank you @Nic Brough -Adaptavist- and @Alex Koxaras _Relational_ . I've pressed the button and it didn't break the system :)

I guess this could be a part of that message, mentioning adding new issue types will not break the existing ones. I think everything works as intended so thank you again very much for the clarifications and your help. Cheers!

[Timofey Yevgrashyn]

May we get back to the first question?  
"I would like to add one more issue type as Epic."

I want to add another Epic-level issue type. I've created a new Issue type (I call it "Container"), but it's of "Base" type and is not "Epic" type on creation.

 Then I did as in the image above - changed the hierarchy for the new type to be on the same level as Epic. (let's ignore for now the cumbersome message that also puzzled me) 

All changes saved, but no effect.
1. New type not possible to use to link tasks to it (neither inside task in Epic field, nor by link from parent to child)
2. new type not visible on Roadmap or "Advanced Roadmap"

Do we have any forecast on when is this "Issue Type Hierarchy" would work as expected?
At the moment admin UI allows to do something that has no effect on the project settings

[Daniela Rodrigues Torchio]

Hi, @Timofey Yevgrashyn

I'm facing the same problem as you were. Did you find a way to solve the problem?

[Alex Koxaras _Relational_]

@Aleksandar Djokic hi and welcome to the community,

I havent experiment a lot with structure, but from your message I underline the "in all company-managed projects in your site". This seems huge..

Can you try on another instance?

[Aleksandar Djokic]

Hi @Alex Koxaras _Relational_ , glad that I've joined. I cannot try this on another instance, it would be good to know in this exact situation whether things would change drastically - we have a lot of projects, some are using more, some are using less Epic. If someone did this exact thing and knows the outcome - that would be the best (I still have no guts to press that button and apply the change :) )

[Roman _Romanik_]

@Aleksandar Djokic , how did you get it? I mean the second issue of the level =1. 
It looks like a miracle to me. There are lot of places, where it is written that it is impossible.
Has anyone managed to reproduce it?  

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

You go to Admin -> Issues -> Issue Type Hierarchy, and click on the field you have pointed to in the screenshot.  That gives you a drop-down list of issue types (divided into selected and available), which you can then click on to add or remove them from that layer in the hierarchy.

[Roman _Romanik_]

@Nic Brough -Adaptavist- , thank you for your reply. It is amazingly quick! 
Yes. I've been to this part of settings, as to any other nook and cranny of them but, as it was mentioned elsewhere, it is not possible to create a second epic-level issue

That's why I cannot reproduce the result of @Aleksandar Djokic 

I thought it was impossible.


 

[Nic Brough -Adaptavist-]

You're in the right place, and the wrong one at the same time!

Your screenshot is of the place where you can create issue types.  You should go ahead and do that, using a standard issue type (not sub-task)

Jira's core only actually has two classes of issue type - base (standard) and sub-task.  You can't create other classes of issue type directly.

Technically, in the background, Epics are base issue types, there's just a pile of code that recognises them and handles them differently, and in systems with Advanced Roadmaps (or certain other apps), more so.

So, to get another issue at the layer of Epic, you need to do two things:

• Create a base level issue type with the name you want
• Follow the instructions in my previous comment to get it added to the Epic layer

[Roman _Romanik_]

Thank you for all your attention, but I definitely miss something, @Nic Brough -Adaptavist- 
I'm sorry for my ignorance. 

1. I have created the much desired Feature issue type at the level 0, i.e. the same level as Story, Task or Bug. 

Then, I go to Admin -> Issues -> Issue Type Hierarchy and see nothing to add to the level of Epic.

My instance of Jira is Cloud, the Plan is Free. 

May the problem be in that? 

[Nic Brough -Adaptavist-]

Note the first line below the menu in your screenshot - you don't have Advanced Roadmaps, so you can't change the hierarchy.

[Roman _Romanik_]

Technically speaking, I don't want 'expand beyond the epic level'. It is explicitly stated to be impossible for a Free Plan. I just want to stay on the epic level, not 'beyond' it. 

Anyway, I suspect this is the quesion of the Premium plan or not. I'd love to have it mentioned somewhere clearly. 

Thank for your effort, Nic!

[Gal Fatal]

Hi

Had similar issue

I needed to create one more issue type at the epic level, and yes it reuires premium.

I switched to premium trial and than it works. You can then add more levels or set more than one issue type in the level of epic.