nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New three level heirarchy (custom issue type)

Shiva Jamei

I want to have a three level heirarch, Parent - Second parent - child (subtask)

I can add different levels in the heirarchy configuration, however it is not working actually.

I have created new custom issue types, two parents and two subtasks, in order to be able to link them correctly to create the three levels.

Accepted answers

Trudy P Claspill

Hello @Shiva Jamei

Jira natively support a three level issue hierarchy:

Level 1 = Epic issue type
|-- Level 0 = "standard" issue types (i.e. Story, Task Bug)
    |-- Level -1 = "subtask" issue types

By default at a global level, for use in Company Managed projects, you can create additional issue types at Level 0 and Level -1.

If you are working with Team Managed projects you can create additional issue types only at level 0, and those are created within each Team Managed project separately.

With the Premium subscription (which you post tags indicate you have) it is possible to add more levels above Level 1, for use in Company Managed projects. You can't add levels above Epic in Team Managed projects, but there is a work-around described here.

Given that information...

Are you working with the issue type hierarchy of a Team Managed project or a Company Managed project?

Can you show us the issue types information for that project from that project's Project Settings?

If you are working with a Company Managed project, can you show us the information from the Issue Type Hierarchy page at:

https://yourURL/jira/settings/issues/issue-hierarchy

And, can you provide more details on exactly what you mean when you say it is "not working"?

All comments

Trudy P Claspill

Hello @Shiva Jamei

Jira natively support a three level issue hierarchy:

Level 1 = Epic issue type
|-- Level 0 = "standard" issue types (i.e. Story, Task Bug)
    |-- Level -1 = "subtask" issue types

By default at a global level, for use in Company Managed projects, you can create additional issue types at Level 0 and Level -1.

If you are working with Team Managed projects you can create additional issue types only at level 0, and those are created within each Team Managed project separately.

Given that information...

Are you working with the issue type hierarchy of a Team Managed project or a Company Managed project?

Can you show us the issue types information for that project from that project's Project Settings?

If you are working with a Company Managed project, can you show us the information from the Issue Type Hierarchy page at:

https://yourURL/jira/settings/issues/issue-hierarchy

And, can you provide more details on exactly what you mean when you say it is "not working"?

Shiva Jamei

Thanks for your response, I have added new issue types that I would like to use for this specefic project which is company based project.

I have "Workstream" as parent, then I would like to open different "Group" under each workstream ticketn ,and each group should have "Action item", which should corrisponds to the usual subtasks.

All the issue types are created.

In the Heirarchy configuration, I can add Workstream and Group, as they are Stanrdard issue types, but I cannot add "Action item" as a subtask.

I read online that I should set the parent child relations as well, I don't know how to do it if needed.

These issue types are active for my project, however I can only create workstream and under those I can create only child tickets, it always remains at two levels.

Trudy P Claspill

In the Heirarchy configuration, I can add Workstream and Group, as they are Stanrdard issue types, but I cannot add "Action item" as a subtask.

When you create a new issue type you specify if it will be a Standard issue type or a Subtask issue type.

Screenshot 2024-11-19 at 9.59.14 AM.png

Based on that selection the new issue type is automatically added to Level 0 or Level -1 of the Issue Type Hierarchy.

The Issue Type Hierarchy screen allows you to "pull" Standard issue types from Level 0 and put them in higher levels (1 and above). If you want a new Standard issue type to remain at Level 0, you do nothing on this screen. For new Sub-task issue types you also do nothing on this screen.

I have "Workstream" as parent, then I would like to open different "Group" under each workstream ticketn ,and each group should have "Action item", which should corrisponds to the usual subtasks.

What you have stated here is that the hierarchy you want is:

Level 1: Workstream
|-- Level 0: Group
    |-- Level -1: "Action item"

This doesn't match what you have shown in your Issue Type Hierarchy screen images, which is

Level 2: Groups
|-- Level 1: Workstream
    |-- Level 0: available Standard issue types
        |-- Level -1: "Action item"

You need to remove "Groups" from Level 2. That will automatically drop it back to Level 0 since it is a Standard issue type.

I read online that I should set the parent child relations as well, I don't know how to do it if needed.

The Issue Type Hierarchy establishes the available parent/child relationships. For any given issue type, its parent must come from the issue types in the level directly above it and its children must come from the issue types directly below it. Based on the images you provided the parent/child relationships are:

Initiatives and Groups can be parents of Epics and Workstreams.

Epics and Workstreams can be parents of all other Standard issue types.

Those other Standard issue types can be parents of Sub-task issue types.

Conversely:

Sub-task issue type parents must be from the group of other Standard issue types

Other Standard issue types parents must be Epics or Workstreams.

Epic and Workstream parents must be Initiatives or Groups.

As I said, the Groups/Workstream relationship you have configured doesn't match your original statement about what you want. You need to remove Groups from Level 2 to fix that.

Shiva Jamei

Thanks for the explanation, it is much more clear for me the logic and how it works, I have deleted the group as level 2.

Workstream is now my level 1.

In the project when I want to create a new ticket I see the Issue type: Workstream which should be level 1 based on hierarchy, and Group which is level 0.

Then I have a workstream ticket, and want to open a Group under it, if I click on Add I see only subtask. am I missing a step?

Level 0 .png

create issue.png

Shiva Jamei

Sure, I didn't delete the standard ones, epic and initiative, I have only kept Workstream as level 1. The grey circle icon is the workstream.

Level 1.png

Shiva Jamei

My company based project is a based on the Task management template, I guess this can be an issue, as I have now created a new project which is Cross team planning, and in this one I can see Epic, as Level 1 and under that I can add Childs.

Shiva Jamei

I have created a new project and the hierarchy model is working with this template. Thanks for the clarification. @Trudy P Claspill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud