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

Hi all,

We don’t have a short-term plan to introduce the ability to insert a new hierarchy level below Epic. Because of that, this request has been marked as Won’t Fix.

A workaround is available by:

• Renaming existing Epic level

• Creating a new hierarchy level above the old Epic level and name that “Epic”

• Assigning your issue types accordingly

Please make sure you read the documentation first before proceeding, and note the FAQ section if you are moving existing issue types to different hierarchies as that will break existing parent and child relationships between your issues, in which we recommend first performing a bulk update to update any issues that may be affected.

Documentation is available here: [Configure your Jira instance to use a custom Agile framework | Jira | Atlassian Documentation|https://confluence.atlassian.com/jirakb/configure-your-jira-instance-to-use-a-custom-agile-framework-1387599403.html]

Regards,

Irene Ongkowidjaja
Product Manager - Jira