Can a new issue type called FEATURE at the level of the standard EPIC issue for 1 specific project.

[Shefali Tayade]

Can a new issue type called FEATURE at the level of the standard EPIC issue for 1 specific project. The FEATURE issue type needs to be a child of INITIATIVE issue types and parent of STORY issue types.

We already have the issue type "feature" in our JIRA instance but the hierarchy level is different. We want to set it for 1 particular project without affecting other project where this issue type "feature" is being used.

[Trudy Claspill]

Hello @Shefali Tayade 

No, that is not possible.

The issue type hierarchy is a global setting that applies to all projects. You cannot have one issue type at different hierarchy levels in different projects.

You would need to use two different issue types that are set at the two different hierarchy levels.

[YY Brother]

Hi @Shefali Tayade 

If you're using Jira cloud premium plan and don't have any other Apps like BigPicture, then you can't implement this requirement.

The issue type hierarchy is at the Jira product level, which will impact all the jira projects in this intance.

However, we could use BigPicture instead to implement it because the issue type hierarchy can be customized at a specific BP program level.

Hope it helps,

YY Bro

[Hannes Obweger - JXL for Jira]

Hi @Shefali Tayade

Jira's hierarchy configuration is global for your site, meaning that you can always only have one.

The only thing I can think of is to use issue links to model your project hierarchy. An issue link can connect any issue with any other issue, so you have complete freedom. The downside is that Jira doesn't really recognise an issue link as a parent/child relationship, and therefore won't give you a lot of hierarchy-related features.

There are, however, a number of hierarchy-focused apps on the Atlassian Marketplace that can do so. E.g., my team and I work on an app in which your use case should be easy to solve: JXL for Jira. 

JXL is a full-fledged spreadsheet/table view that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including the support for configurable issue hierarchies. These issue hierarchies (a.k.a. structures) can be based on Jira's built-in parent/child relationships (like epic/story, or task/sub-task), and/or based on issue links of configurable issue link types (like is parent of / is child of).

E.g., this is an example of a hierarchy with sub-sub-tasks, which isn't normally possible in Jira:

In this example, WORK-363 and WORK-364 are connected via issue links. Note that this hierarchy wouldn't be global by any means, but really only be visible in this specific JXL sheet.

Any questions just let me know,

Best,

Hannes

[Rahul_RVS_Support]

Hi @Shefali Tayade 

As mentioned by everyone, Issue Hierarchy changes will impact all the projects. However you can use Issue Links to create a hierarchy per project and not impact others. For that you would need a mktplace app to visualize and manage the same. If you would be interested to try one out do take a look at

Issue Hierarchy 

In the video below, we have a "New Issue" type which is being set as a parent of Epic using issue links.  The app has multiple other features including roadmaps which are very useful in project tracking and management and is free for upto 10 users.

(Disclaimer: I work for RVS, the vendor for this app)