Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-4446

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

XMLWordPrintable

    • 19
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Atlassian Update – 6 November 2017

      Hi all,

      Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer.

      We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to invest in more extensive issue hierarchies in Jira. Therefore we decided to close this issue.

      While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level.

      Jira as a tool promotes agile approach to project management, where simplicity is key and teams work iteravely to deliver small sections of a project at a time. We strongly believe that current hierarchy of epic, task (story) and subtask supports this approach.

      Meanwhile, as Atlassian, we understand that growing teams may require more flexibility. This is why we are investing in Advanced Roadmaps for Jira (formerly known as Portfolio for Jira). Advanced Roadmaps extends Jira hierarchy with the concept of initiative and helps organise and prioritise your team's work to build a realistic roadmap that spans multiple teams and Jira projects.

      Also there is a commercial third party plugin available, Structure that provides the ability to create a hierarchy of issues for Jira Server customers.

      Since investing in more extensive issue hierarchies in the Jira platform is not aligned with our strategy and roadmap, we will be closing this issue. I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. Please don't hesitate to contact me if you have any questions.

      Regards,
      Gosia Kowalska
      Senior Product Manager, Jira Server

      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
          jira-2.jpg
          84 kB
        2. jira-3.jpg
          jira-3.jpg
          214 kB
        3. lh_od_1.png
          lh_od_1.png
          76 kB

              Unassigned Unassigned
              e4f74cf81faf Mark Derricutt
              Votes:
              1259 Vote for this issue
              Watchers:
              619 Start watching this issue

                Created:
                Updated:
                Resolved: