Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How make issue structure deeper?


Currently I can organise tasks only in such way:

Epic -> Story -> Subtask


Epic -> Task -> Subtask


And I would like to have the following:

Epic -> Story -> Task -> Subtask


Is there a setting in Jira so I can get what I need? May be there is a plugin?

3 answers

1 vote
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 28, 2019


  Jira by default allow for Epics -> Issue -> Sub-Task.  A story and a task are both just issues.  If you want to go deeper than that you would need an app that can help you do this.  Plugins like Structure and Big Picture can help organize jira issues however you would like them to display in the apps interface.

Structure -

Big Picture -

0 votes
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jul 10, 2020 • edited

Hello Andrey,

In BigPicture/BigGantt, you can automatically create a no-limited number of WBS levels. Task Structure can be created based on both build-in task attributes (e.g., Epic link, Component, Version, Sprint) as well as links.

To achieve hierarchy: Epic >> Story >> Task >> Subtask, you can set the suitable rules, by activating respective structure builders in Program Configuration (Epic, Subtask). The exception is the "Story >> Task" dependency. Use a link-based constructor here, e.g., Parent to child relation (or another custom link) after prior linking them in Jira. It is important that the link direction must be legible from Jira's level. 

Tasks newly added to the program will follow the rules currently defined in the structure builders' settings. See my images as a reference.



Please note that the order of structure builders will determine different levels of the hierarchy, or in other words, the first structure builder determines the highest level within the structure.

More detailed information you will find in our article Program Box configuration - Task - Task structure.

If you have further questions, please let me know.

0 votes
Dave Rosenlund _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 01, 2019

Hello, @Andrey Ponomarenko@Brant Schroeder is correct. Structure and Big Picture are the two most popular solutions for this. 

It looks like you may have used Structure for Jira for a time back in 2015.  A lot has changed since then. Please let us know if we can help you achieve your hierarchy goals.

You can reach out to us via at any time if you'd like some tips.


-dave [ALM Works]

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events