Details
-
Suggestion
-
Resolution: Unresolved
-
14
-
Description
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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.
Attachments
Issue Links
- is related to
-
JSWCLOUD-19407 Ability to add hierarchies below an Epic in Jira
- Closed
-
JPOSERVER-1482 Make mapping of Epic issue type and below configurable in Live Plans hierarchy configuration
- Gathering Interest
- was cloned as
-
JSWCLOUD-19880 Unable to set other standard issues below epic
- Closed