• 31
    • 5
    • 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
          Eowf8BJUUAEn86Y.jpg
          34 kB
        2. issuesInEpic.png
          issuesInEpic.png
          102 kB

            [JRACLOUD-76878] Ability to change the order of the Issues in Epic

            Is it possible to add a custom field in the order by drop down 

            Sudha Bharathi added a comment - Is it possible to add a custom field in the order by drop down 

            Atlassian Update - March 2023

            As previously discussed here, we've found that this ticket is a duplicate of the request JRACLOUD-76877 – Move issues up and down in Epic to any desired position (manual re-order rather than sort)

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - March 2023 As previously discussed here, we've found that this ticket is a duplicate of the request JRACLOUD-76877 – Move issues up and down in Epic to any desired position (manual re-order rather than sort) We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - - edited

            I believe the issue JRACLOUD-76877Move issues up and down in Epic to any desired position was created when this one, (JRACLOUD-76878) was incorrectly closed. JRACLOUD-76877 now has far more votes so I would like to close this one as a duplicate, otherwise, we risk splitting votes.

            Please let me know if you disagree with this proposal. Thanks!

            Anusha Rutnam added a comment - - edited I believe the issue  JRACLOUD-76877 – Move issues up and down in Epic to any desired positio n was created when this one, ( JRACLOUD-76878 ) was incorrectly closed. JRACLOUD-76877 now has far more votes so I would like to close this one as a duplicate, otherwise, we risk splitting votes. Please let me know if you disagree with this proposal. Thanks!

            This is becoming a major issue in our organization.  Processes change all the time and recreating Epics with 20+ tasks as a template is very inefficient. - It defeats the purpose of getting Deep Clone even with the Rank setting.  Additionally, my Stories were automatically rearranged, and it is creating a lot of confusion especially since I have multiple teams/project boards involved. 

            Griselda Priest added a comment - This is becoming a major issue in our organization.  Processes change all the time and recreating Epics with 20+ tasks as a template is very inefficient. - It defeats the purpose of getting Deep Clone even with the Rank setting.  Additionally, my Stories were automatically rearranged, and it is creating a lot of confusion especially since I have multiple teams/project boards involved. 

            +1.

            I can't believe such a basic thing is missing. If it's too complicated add the "Sort by Name" so I can at least add a number prefix.

            This is one major reason why I still need to waste time generating spreadsheets, ppts, or other visual supports for communication and quarterly planning.

            osvaldofernandez added a comment - +1. I can't believe such a basic thing is missing. If it's too complicated add the " Sort by Name " so I can at least add a number prefix. This is one major reason why I still need to waste time generating spreadsheets, ppts, or other visual supports for communication and quarterly planning.

            +1

            Ka Silveira added a comment - +1

            Roy Gunter added a comment -

            +1 An EXTREMELY important time saver for me.

            Roy Gunter added a comment - +1 An EXTREMELY important time saver for me.

            Nik added a comment -

            +1

            Nik added a comment - +1

            Can Aydin added a comment -

            +1

            Can Aydin added a comment - +1

            +1

            Paula Dasch added a comment - +1

              yjiang@atlassian.com Yuan Jiang
              12ee0a4b8cbf Adrian Yong
              Votes:
              104 Vote for this issue
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: