Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: None
Labels:

UIS:
0
Support reference count:
14
Feedback Policy:

JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

Description

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

Problem:
The epic issue type is hard-wired to the 2nd hierarchy level in Portfolio (one above the lowest standard issue types level and two above the sub-tasks level). This can be limiting in case more hierarchy levels are required under the epic issue type.

Workaround:
For the time being, another issue type needs to be used to fulfil the purpose of the epic issue type. This type can then be mapped to any hierarchy level and thus will allow for more hierarchy levels below.

Solution:
Allow mapping the epic issue type to other hierarchy levels and also allow for the levels below to be changed too.

Attachments

Issue Links

is duplicated by

JPOSERVER-1850 Hierarchies below an Epic in Portfolio for JIRA

Closed

JPOSERVER-1853 Unable to set other standard issues below epic

Closed

relates to

JSWCLOUD-19729 Make mapping of Epic issue type configurable in Live Plans hierarchy configuration

Gathering Interest

was cloned as

JPOSERVER-1853 Unable to set other standard issues below epic

Closed

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

(3 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Albert Kavelar

Archiver:: Aakrity Tibrewal

Dates

Created:: 22/Jun/2016 1:22 AM

Updated:: 30/Aug/2023 3:41 AM

Archived:: 12/Oct/2023 2:33 AM