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

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

XMLWordPrintable

    • 0
    • 14

      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.

            Assignee:
            Unassigned
            Reporter:
            Albert Kavelar
            Archiver:
            Aakrity Tibrewal

              Created:
              Updated:
              Archived: