Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Do
Component/s: Issue - View
Labels:

UIS:
51
Support reference count:
92
Feedback Policy:

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.

Description

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

Atlassian Update – 17 June 2022

Hi all,

The Jira Software Premium edition now allows you to create as many levels as you like above epic, with as many issue types as you like at each level, this applies to all company-managed projects in your Jira Software instance. See our guide here on setting up your issue hierarchy above epic.

For those who want a custom issue hierarchy per project, there is a third party plugin available Structure

For those trying to implement a SAFe issue hierarchy (Story -> Feature -> Epic) we have an upcoming feature called Epic Renaming aimed at addressing this use case.

Creating levels below sub-tasks is not in our plans at the moment, we hope the above solutions are sufficient to help you structure your work.

Regards
Rohan Swami
Jira Software Product Manager

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

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

Closed

duplicates

JRACLOUD-3639 Issue hierarchy

Closed

is duplicated by

JRACLOUD-28547 Allow stories to aggregate issues from multiple projects

Closed

JRACLOUD-30912 Subtask's subtasks

Closed

JRACLOUD-33244 Allowing nested tasks

Closed

JRACLOUD-45981 Create subtask under existing subtask

Closed

is related to

JRACLOUD-5869 Sub-Task should have independent security levels

Closed

JRACLOUD-7824 Create a Linked Issue operation

Closed

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

Closed

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

Closed

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

Closed

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

Closed

relates to

JRACLOUD-846 Support for subcomponents

Gathering Interest

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

Gathering Interest

JSWCLOUD-15412 Improve JIRA Software interface and issue linking

Gathering Interest

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

(1 is duplicated by, 6 is related to, 3 relates to, 6 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Mark Derricutt

Votes:: 1318 Vote for this issue

Watchers:: 629 Start watching this issue

Dates

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

Updated:: 27/Mar/2024 12:39 AM

Resolved:: 17/Jun/2022 5:43 AM