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

Associate an 'Epic Link' value to an Epic by automatically assigning it the Epic's 'Epic Name' value to allow filtering of Epics and Stories by Epic Link

XMLWordPrintable

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

      Problem:
      -----------
      Currently there is no way to view the list of stories per epic in a jira query or any view to show the epic-story hierarchy.
      fig 1;
      Epic x
      Story 1 of Epic x
      Story 2 of Epic x
      Story 3 of Epic x
      Story 4 of Epic x

      Yes, you can do this on the rapid board by selecting the epic in the epic panel to filter the stories of that epic but it doesn't provide a custom view of the various fields you wish to compare that you get from a jira filter with selected columns.

      As a Program Manager I constantly encounter this challenge as do many other functional groups such as Product Management. We find it to be an important view in initial planning of a release.

      If Epic Link was sortable (GHS-10130) we'd at least be able to achieve the list of stories per Epic even if the epic wasn't shown.
      fig 2;
      Story 1 of Epic x
      Story 2 of Epic x
      Story 3 of Epic x
      Story 4 of Epic x

      Enhancement Request:
      ------------------------------
      The 'epic link' value on a story is the Epic's 'epic name' field value.
      Could you please consider enhancing the Epics to have an Epic Link value automatically assigned to it based on its 'epic name' value.
      This could be non-editable or even hidden on an epic.
      It would allow a jira query to return the epic and story using the epic link field.

              Unassigned Unassigned
              john.garrett John Garrett
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: