Issue type Hierarchy - Add new issue type in Issue hierarchy

[ranjanajindal]

My project requirement is that the parent and child relationship is as follows

Parent  Issue Type             Child Issue Type

Epic                                    Feature

Feature                               Story

Story                                   SubTask

In Issue type Hierarchy i need Epic at level 2, Feature at Level 1, Story at 0, Task also at 0, Subtask at -1.

Is it possible to change the Epic level to 2 and add anew issue type at level1.

If I make the change at my site of JIRA cloud Instance will it impact the issues of other projects in same instance.

In JIRA can we use the change only for particular project.

[Tomislav Tobijas _Koios_ · Accepted solution]

Hi @ranjanajindal ,

To my knowledge, Epic cannot be moved to another level. I would suggest checking JAC and the following filter when it comes to issue hierarchy: component = "Issue - Type Hierarchy" AND statusCategory != Done 

As for the second part regarding issue hierarchy configurable per specific project, here's an open suggestion on that: JSWCLOUD-21815 As a user I want to have the ability to make Advanced roadmap hierarchy configurable per project on Jira software 

If there's no suggestion related to changing the Epic level, you might want to try to reach out to Atlassian Support for them to check and potentially create a new suggestion on JAC.

Cheers,
Tom

[Trudy Claspill]

Hello @ranjanajindal 

Are you using a Premium subscription? Extending the issue hierarchy is supported only in Premium and Enterprise subscriptions.

Assuming you have such a notification...

 It would be possible to change the name of the current Epic issue type to Feature. All functionality related to the Epic issue type would stay with the issue type after its rename to Feature.

You could then add a new standard issue type and call it "Epic", and then move that issue type to be above "Feature". Note that new "Epic" issue type would not have the functionality associated with the issue type now named "Feature".

Any changes to the issue type names or hierarchy will impact all Company Managed projects.

Note that if you are working with Team Managed projects, extending the issue hierarchy within the project is not supported. Instead you have to extend the hierarchy at the Global configuration level, and then the issues above level 1 must be created in Company Managed projects. You can then link the Level 1/Epic issues in the Team Managed project to the higher level issue in the Company Managed project.

[ranjanajindal]

I am using Enterprise version

[Trudy Claspill]

Then your environment supports the capability to extend the issue hierarchy globally, affecting all Company Managed projects. Refer to:

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

As I noted, if you want an extended hierarchy applied to a Team Managed project you have to use a Company Managed project for the levels above Epic/Level 1.

[Hannes Obweger - JXL for Jira]

Hi @ranjanajindal

you may already know that Jira Premium allows additional hierarchy levels, however these hierarchy levels are always only on top of epics. Adding something below epics is possible, but tricky - see this thread for a thorough discussion on the matter.

As you'll see in the linked discussion, one way to implement your exact hierarchy could be via issue links. Issue links give you full flexibility in how you want to model your hierarchy, and unlike Jira Premium's hierarchy configuration, don't globally impact your Jira site.

The downside is that issue links aren't natively recognised as parent/child relationships, so you won't get a lot of hierarchy-related features out of the box. This being said, if you're open to solutions from the Atlassian Marketplace, there's a number of hierarchy-related apps available that can help with this.

E.g., this is how your hierarchy could look in the app that my team and I are working on, JXL for Jira:

(In this example, features and stories are connected to each other via issue links.)

Any questions just let me know,

Best,

Hannes