Hierarchy sub-levels with Jira Premium

[Test Test]

Dear all,

I'm testing the Jira Premium and the hierarchy side.

I could create additional levels on top of the hierarchy, but I wasn't able to add an additional sub-level, i.e. level -2.
Do you know if there is a way to do it ?

I wanted to keep Epic at level 1 and story at level 0, and define tasks with level -1 and sub-tasks with level -2

Thank you for your help

Nancy

[Hannes Obweger - JXL for Jira · Accepted solution]

Hi @Test Test

welcome to the community.

Jira only allows adding additional hierarchy levels on top of epics, but not below. To the best of my knowledge, there are no plans to lift this limitation.

Two ways forward: 

a.) You could consider "lifting" your entire model up by one level, so that what you currently envision to be "-2" becomes "-1" (i.e., sub-tasks), and so on. Just keep in mind that Jira has opinions on the standard hierarchy levels (-1, 0, 1), e.g. in terms of what can be added to a sprint, etc. etc., and while you can e.g. "re-imagine" a sub-task to now be a story, you can't change these limitations.

b.) You may already know that you can use issue links to establish any relationship between any pair of issues, and nothing stops you from establishing a "is parent of/is child of" relationship between a sub-task and a "sub-sub-task". Here, keep in mind that Jira won't "understand" this issue link as a parent/child relationship. There are, however, a number of hierarchy-related apps in the Atlassian Marketplace that can do so. I myself happen to work on such an app; I'll provide more details below.

Hope this helps,

Best,

Hannes

[Test Test]

Thanks Hannes for the explanation and the ways to consider, very helpful.

[Hannes Obweger - JXL for Jira]

Very welcome @Test Test!

Just to expand on the last point, here's how this would look in the app that my team and I are working on, JXL for Jira - note how WORK-363 is a "sub-sub-task" below WORK-364:

JXL is a full-fledged spreadsheet/table view for your issues 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 support for (configurable) issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like epic/story, or story/sub-task), as well as issue links. Above, I'm using issue links of type is parent of/is child of to model an additional hierarchy level below sub-tasks.

Any further questions just let me know,

Best,

Hannes

[Mohammed Aamer Khan · Accepted solution]

Hi @Test Test

JIRA does not have a changeable hierarchy.

For mor information please refer another question raised in community Click Here