[JRACLOUD-4446] Sub-issues should be able to contain their own sub-issues - Create and track feature requests for Atlassian products.

Details

Type: Suggestion
Status: Gathering Interest (View Workflow)
Resolution: Unresolved
Component/s: Issue - View
Labels:

UIS:
74
Support reference count:
49
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 – 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.

Regards,
Dave Meyer
dmeyer@atlassian.com
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.

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

Gathering Interest

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-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

JRACLOUD-7824 Create a Linked Issue operation

Gathering Interest

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)

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

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates