Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-26548

Extend the Epic features to the new custom Epic hierarchy level instead of the Epic issue

XMLWordPrintable

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

      In light of recent updates, Admins can add hierarchies below an Epic in JIRA, which led them to anticipate that the new Epic level would inherit the same functions and features as the old Epic level.

      To illustrate, we have the following issue hierarchy:

      • 3 Initiative
      • 2 Epic (New)
      • 1 Story (Renamed Epic issue)
      • -1 Task
      • 0 Subtask

      Currently, features such as the panel in the backlog are tied to the original Epic issue type. The epic name change is not reflected in the backlog when creating an Epic , in reports- cycle time Jira, Sprit insights 

      This suggestion is to have these features tied to the level named Epic instead of the issue type Epic that exists at level 1.

              Unassigned Unassigned
              e0bbe77fe18a Hala ElRoumy
              Votes:
              12 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: