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

Ability to change the order of the Issues in Epic

XMLWordPrintable

    • 115

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

      Atlassian update on June 21st

      Hi everyone, thanks so much for your suggestions.

      You can now see a new dropdown box that allows users to sort issues under epic issues (company managed projects) and child issues (team managed projects). The following sort options could be available to you, based on your specific project setup:

      • Created (most recent first)
      • Key (alphabetically then numerically)
      • Priority (same order specified in the global admin - only available when the “parent issue” also has the priority field visible)
      • Status (first by status category - to do, in progress, then done - and then alphabetically
      • Assignee (alphabetically then unassigned)
      • Default (current order, “ranking” - for example, what was set in a board)

      Atlassian Product Team

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

      Today we don't have the ability to reorder the Issues in Epic when viewing a ticket.
      It would be great if we can rank them like we do with the Sub-Tasks (see attached).

      Also, it would be helpful to have a header column to the "Issues in this epic" section of an epic where the users could sort by issue key, ID, or summary

        1. Eowf8BJUUAEn86Y.jpg
          34 kB
          Kate C.
        2. issuesInEpic.png
          102 kB
          Andre Quadros Petry

              yjiang@atlassian.com Yuan Jiang
              aquadrospetry Andre Quadros Petry (Inactive)
              Votes:
              1438 Vote for this issue
              Watchers:
              400 Start watching this issue

                Created:
                Updated:
                Resolved: