Can't I increase the depth of the project's sub-issues?

Question

The structure of the organization I currently belong to is as follows.
First, write the name of the project at the top and
Below that, write down the assigned roles for the project.
There is a large chunk of work distributed to each role below, but there are no problems up to this point. However, I want to add detailed tasks within a large chunk, but no more sub-issues are created. It would be great to have just one more depth, but the lack of one sub-issue makes it difficult to work efficiently and is disappointing from the user's perspective.

Hannes Obweger - JXL for Jira · Answer

Just to expand on the last point, this is how this would look in the app that my team and I are working on, JXL for Jira; as you can see, we've modelled a hierarchy with two levels of sub-tasks:

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 range 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 task/sub-task, or whatever you may have modelled in Advanced planning), and/or based on issue links of configurable issue link types.

Any questions just let me know!

Hannes Obweger - JXL for Jira · Answer

Hi @최선하,

welcome to the community! One more thing to consider is the use of issue links; issue links can signify any relationship between any pair of issues, and hence can be used to create parent/child relationships that go beyond Jira's built-in parent/child relationships. There's a pre-configured is parent of/is child of issue link type, but you can model your own.

The big problem is that Jira doesn't 'understand' issue links as parent/child relationships, so it won't give you many hierarchy-related features out of the box. As Nic mentioned, there are options available from the Atlassian Marketplace that can help with this.

Hope this helps,

Best,

Hannes

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

Jira's hierarchy is pretty much fixed.  Sub-tasks are fragments of their parent base-level issue, not really independent issues.  Base-level issues can be grouped into Epics, Epics can be grouped by higher layers, if you have access to Advanced planning.

There are some apps that might be worth looking at - Structure and Hierarchy for Jira can help with more layers.