[JSWCLOUD-9455] Ability to create a hierarchy of Epics instead of a single level - Create and track feature requests for Atlassian products.

Type: Suggestion
Resolution: Fixed
Component/s: Classic - Boards
Labels:
- affects-server
- jsw-s7
- odysseus
- p2
- triaged

UIS:
40
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.

In Version One, we could create a hierarchy of Epics, but we don't seem to have this capability in Greenhopper. Is this something that can be provided?

is blocked by

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

Closed

is duplicated by

JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software

Closed

JSWCLOUD-5356 Story Hierarchy support in Greenhopper

Closed

JSWCLOUD-8044 As an admin, I would like to be able to configure a hierarchy navigator with an issue type(s) so that it would know how to build a tree, on a given issue

Closed

JSWCLOUD-8755 Integrate Structure and Sprint Planning

Closed

JSWCLOUD-9045 Support for Groups of Epics or Themes

Closed

JSWCLOUD-9077 Add the ability to separate subtasks from parents

Closed

JSWCLOUD-9444 It would be great to be able to easily create heirarchies of Issues, Components and Versions

Closed

JSWCLOUD-9809 Ability to link issues to stories and not just epics

Closed

is related to

JSWCLOUD-2420 As a GH user, I want to work with a tree view of my epics within the planning board

Closed

JSWCLOUD-11665 Assign Sprints to Subtasks and Parent Reflects Current Subtask Sprint Estimation

Closed

JSWCLOUD-18875 Add issue type between Epic and Story

Closed

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

(4 is duplicated by, 3 is related to, 5 mentioned in)

Type: Suggestion
Resolution: Fixed
Component/s: Classic - Boards
Labels:
- affects-server
- jsw-s7
- odysseus
- p2
- triaged

UIS:
40
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.