Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Do
Fix Version/s: None
Component/s: Issue - Sub-Tasks
Labels:

Support reference count:
19
Feedback Policy:

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.

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

jira-2.jpg
84 kB
13/Jul/2016 5:36 AM
jira-3.jpg
214 kB
13/Jul/2016 5:37 AM
lh_od_1.png
76 kB
05/Oct/2014 10:28 AM

Issue Links

blocks

JSWSERVER-9455 Ability to create a hierarchy of Epics instead of a single level

Gathering Interest

duplicates

JRASERVER-3639 Issue hierarchy

Closed

is duplicated by

JRASERVER-5273 More than 2 levels of subtasks

Closed

JRASERVER-9361 Unlimited levels of Sub-tasks hierarchy

Closed

JRASERVER-15169 Ability to define a Issue Hierarchy

Closed

JRASERVER-17455 Subtask of a Subtask (sub-sub-task)

Closed

JRASERVER-20651 child tasks

Closed

JRASERVER-25236 Ability to create sub-sub tasks

Closed

JRASERVER-28547 Allow stories to aggregate issues from multiple projects

Closed

JRASERVER-30912 Subtask's subtasks

Closed

JRASERVER-33244 Allowing nested tasks

Closed

is incorporated by

JRASERVER-2544 Graph link dependency map

Closed

JRASERVER-12241 Support for Product Suites / Sub-Projects

Closed

is related to

JRASERVER-5869 Sub-Task should have independent security levels

Closed

JRASERVER-24776 Allowing sharing a sub-task among parent tasks

Closed

JRASERVER-24836 Create sub-task for an issue in another project

Closed

JRASERVER-25008 Directed-Acyclic-Graph view of blocks links to create PERT chart

Closed

JRASERVER-7824 Create a Linked Issue operation

Gathering Interest

relates to

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

Closed

JRASERVER-846 Support for subcomponents

Closed

JRASERVER-5410 Subtaskify issues

Closed

JRASERVER-5617 Change a sub-task to be a normal issue

Closed

JRASERVER-22942 remove sub-tasks as a unique issue type -- sub-tasks should represent a relationship, not an issue type

Gathering Interest

JSWSERVER-15412 Improve JIRA Software interface and issue linking

Gathering Interest

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...

(6 is duplicated by, 2 is incorporated by, 5 is related to, 6 relates to, 20 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Mark Derricutt

Votes:: 1259 Vote for this issue

Watchers:: 619 Start watching this issue

Dates

Created:: 03/Sep/2004 5:44 AM

Updated:: 16/Aug/2022 10:46 PM

Resolved:: 05/Nov/2017 11:26 PM