• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Customer would like to request on the following:

      "As a user of JIRA Agile, I would like to be able to rank epics and stories.
      Given two epics A and B where A is more important to finish first due to business priority than B, I expect epic A and ALL stories contained within epic A to have higher priority/ranking than epic B and all its stories. It seems that the current version of JIRA Agile does not support this since ranking of stories is left untouched when dragging epics up and down in the Plan view.
      Also when creating filters I want to group stories within their epics sorted in priority order. Thus, I would like stories grouped by epic, then sorted on epic rank and within each epic, on story rank."

          Form Name

            [JSWSERVER-9788] Sort on Epic Rank and then Story Rank

            Bill Sim added a comment -

            I'm picking no one is looking at this? The proposed solution by Michael Tokar above is not useful for a backlog with any more than a few Epics. We have about 250 Epics to order, and move their tasks up and down with respect to each other... We want to have Story/Task rank follow their Epic rank somehow...

            Bill Sim added a comment - I'm picking no one is looking at this? The proposed solution by Michael Tokar above is not useful for a backlog with any more than a few Epics. We have about 250 Epics to order, and move their tasks up and down with respect to each other... We want to have Story/Task rank follow their Epic rank somehow...

            Is there an update based on the comment above? 

            amy schneider added a comment - Is there an update based on the comment above? 

            This suggestion is cumbersome at best for large projects and teams. The ability to more finely control how Rank is assigned in the first place (via filter sorting or some other method besides dragging and dropping issues one at a time or in small groups) would make the existing sort by rank much more user friendly.

            Kimberly Kohler added a comment - This suggestion is cumbersome at best for large projects and teams. The ability to more finely control how Rank is assigned in the first place (via filter sorting or some other method besides dragging and dropping issues one at a time or in small groups) would make the existing sort by rank much more user friendly.

            This can be achieved today by using the Epic Filtering functionality on Plan Mode, combined with the ability to select multiple issues at once.

            Example:

            1. Go to Plan Mode where Epic A and B and their issues are present.
            2. Click on Epic A to see only the issues of Epic A
            3. Select all issues of Epic A by clicking on the first, hold down Shift, and then select the last issue
            4. Click and drag the first issue (and thus all of the issues) to the top of the backlog
            5. Unselect the Epic

            This should rank all issues of Epic A above other issues.

            Michael Tokar added a comment - This can be achieved today by using the Epic Filtering functionality on Plan Mode, combined with the ability to select multiple issues at once. Example: Go to Plan Mode where Epic A and B and their issues are present. Click on Epic A to see only the issues of Epic A Select all issues of Epic A by clicking on the first, hold down Shift, and then select the last issue Click and drag the first issue (and thus all of the issues) to the top of the backlog Unselect the Epic This should rank all issues of Epic A above other issues.

              Unassigned Unassigned
              dchua Daryl Chuah (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: