Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-88048

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

XMLWordPrintable

    • 38
    • 30

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

      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 1st hierarchy level in Plans (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.

              Unassigned Unassigned
              akavelar Albert Kavelar
              Votes:
              29 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated: