Additional Work Type Hierarchy Level

[Jason Patrick]

I have set up a Team Managed Project in Jira Cloud Premium. Currently the project is using the default hierarchy for Software Projects:

Epic (level 1)
|-- standard issue types (level 0) i.e. Story, Bug, Task
    |-- subtask issue types (level -1)

What I would like to do is move Epic to Level 2 and have that as a parent of Feature. Then have Feature as a parent to Standard issue types. 

I have read that you can add Initiative in as Level 2, with Epic staying as Level 1, thus adding the additional hierarchy. That would be fine as well, but not sure how to add that to a Team Managed project. If it has to be Company Managed that's fine, I can set it up again. However, I'm not sure how to make Epic a child of Initiative.

To sum up, I would like to have a Level 2 as Parent of Level 1. Level 1 as Parent of Standard Issue types, as well as maintaining Subtask issue types.

Any help anyone can provide would be very appreciated!

[Trudy Claspill · Accepted solution]

Hello @Jason Patrick 

Welcome to the Atlassian community.

Your requirement can be met. You can keep your Team Managed project, but you will have to add a Company Managed project to contain the Level 2 issues.

https://community.atlassian.com/forums/Advanced-planning-articles/Parenting-a-team-managed-epic-with-a-company-managed-initiative/ba-p/2638197

Team Managed projects are limited to the three-level hierarchy.

To get an addition level (level 2) requires:

- Modifying the global Issue Type Hierarchy to add an issue type to level 2

- Create a Company Managed project where the level 2 issues are created, because Team Managed projects don't directly support anything beyond the native 3 levels.

- Create a Plan (from the Plans menu) that has as sources both the Team Managed project and the Company Managed project where your level 2 issues exist

- To make a Team Managed project "Epic" a child of the Company Managed project "Initiative", refer to https://support.atlassian.com/jira-software-cloud/docs/link-issue-to-a-parent-in-advanced-roadmaps/

[Tinker Fadoua]

@Trudy Claspill  we are using SAFe in DC and were told after migration to Cloud we can have the hierarchy we have in DC which is more than the 3 levels

[Trudy Claspill]

Hello @Tinker Fadoua 

I'm not sure of the point you are trying to make in response to my answer. I did not say anything that contradicted your statement.

You can have a hierarchy of more than the default 3 levels in Jira Cloud if you have a Premium or Enterprise subscription.

The additional hierarchy levels must be defined in the Global Issue Type Hierarchy configuration.

The issue types at levels 2 and above can be created only in Company Managed projects. You can't have more than 3 levels in a Team Managed project.

But you can have Epics (level 1) issues in a Team Managed project be children of level 2 issues in a Company Managed project.

[Tinker Fadoua]

My misunderstand, my apologies @Trudy Claspill 

[Jason Patrick]

Thank you so much Trudy! I actually just created a Company Managed Project and Created the Work Type Schema that I wanted using Initiative as Level 2. What I had failed to do previously was to Associate it with the project (which is why when I first tried it didn't seem to work). 

It seems that with Initiative at Level 2 it natively adopts the Parent role for Epics and Epics adopt the Parent role for Stories, so this is exactly what I need. I appreciate all the help!!!

I'm just going to move what I had in the Team Managed Project into the new Company Managed Project since we are in very early stages. Plans look like they might be VERY beneficial though, so will start my learning process with them soon.

Thank you again!

[Tinker Fadoua]

Welcome to the Atlassian Community @Jason Patrick !

I am afraid to say that is not an available option for team managed projects.

Best,

Fadoua

[Dave Mathijs]

Hi @Jason Patrick welcome to the Atlassian Community Forums!

💡Don't create team-manage projects ... thank me later. 😉

Please read the following documentation article: Configure the work type hierarchy

[Jason Patrick]

Note taken. Thanks!

[Rajat Singh]

@Tinker Fadoua @Jason Patrick What if we create an empty Company-managed project in Jira and include both Company-managed and Team-managed projects in an Advanced Roadmaps plan? That way, we can still use the custom hierarchy levels.

[Tinker Fadoua]

@Rajat Singh  it will only apply to Company Managed Projects. Not the team one