Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-4446

Sub-issues should be able to contain their own sub-issues



    • 61
    • 92
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 31 December 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are not currently any plans to implement this suggestion.

      While we absolutely understand many the logic behind many of the requests for more extensive issue hierarchies in JIRA, we strongly believe that our focus should be on making JIRA simpler and easier to use. Simply put, additional levels of hierarchy will add complexity on a conceptual level, at a technical level (more bugs and slower performance) and will lead to a more confusing UI.

      In the mean time there is a commercial third party plugin available, Structure that provides the ability to create a hierarchy of issues for JIRA Server customers.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Dave Meyer
      Product Manager, JIRA Platform

      Original request description:

      As a JIRA user I need more hierarchical organisation of tasks. As of today JIRA offers only a two-level hierarchy (if installed without plugins): stories and subtasks. But in reality the process of resolving issues can be much more complicated. During the process of analysis a simple story can be broken into a number of sub-tasks. And then each of the sub-tasks may be consequently broken into a set of even more granular entities. JIRA does not support an easy way of handling multiple levels of hierarchy in a natural way and the available workarounds require additional steps which render the solution suboptimal.


        1. jira-2.jpg
          84 kB
        2. jira-3.jpg
          214 kB
        3. lh_od_1.png
          76 kB

        Issue Links



              Unassigned Unassigned
              e4f74cf81faf Mark Derricutt
              1316 Vote for this issue
              631 Start watching this issue