can we create a issue type hierarchy without impacting other projects hierarchy

[Trinath_Putchala]

I would like to introduce features as a hierarchy in between EPIC and Story for a specific project. This new hierarchy created should not impact other projects Issue type hierarchy, how to achieve the same in Jira

[Tomislav Tobijas _Koios_]

Hi @Trinath_Putchala ,

If you're on Premium plan, you can configure issue type hierarchy and add custom hierarchy levels.

However, as official docs state, changes to the hierarchy will apply to all company-managed projects.

Potentially, you could set Feature issue type on the same level as the Epic and then create custom Epic issue type and set it above. Then you can configure issue type scheme for that specific project so it only contains Feature and custom Epic and you'll probably get what you'd like.

But, again, this would impact all company-managed projects so whenever someone else uses Feature or custom Epic within their projects, the same hierarchy will be applied.

Note that with the existing approach, if all other projects use Epic - Story - Sub-task hierarchy, this configuration will remain.

Cheers,
Tobi