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

Ability to add hierarchies below an Epic in Jira

XMLWordPrintable

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

       

       

      Update on 15th Aug 2024

      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

       

       

      Problem Definition

      It's not possible to create hierarchies below an Epic in Jira.

      Suggested Solution

      Make it possible to create hierarchies below an Epic.

              Unassigned Unassigned
              skorte Soane Korte (Inactive)
              Votes:
              138 Vote for this issue
              Watchers:
              130 Start watching this issue

                Created:
                Updated:
                Resolved: