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

      As a team-member or product owner
      I want to see issues in the ongoing sprint ordered according to priority
      so that I know what issue to fix next.

      When I view the current sprint in my "Work-tab" (rapidBoard.jspa?...view=detail) I want to view all my items ordered with highest priority on top. This is true for issues without subtasks. If however, I have subtasks among the issues, those issues together with the subtasks are displayed on top. I cannot figure out their priority in relation to the other issues.

          Form Name

            [JSWSERVER-5996] Display issues with subtasks according to priority

            Please watch the duplicate issue for updates.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Please watch the duplicate issue for updates. Regards, JIRA Agile Team

            I cannot understand why this issue has so less votes. I often have to make dummy sub-tasks to have the stories in their right order so that they don't get overlooked by the team.

            Matthias Küng added a comment - I cannot understand why this issue has so less votes. I often have to make dummy sub-tasks to have the stories in their right order so that they don't get overlooked by the team.

            The workaround doesn’t seem to work in version 6.2.5.1 anymore. When I change from Stories to Queries there are no swimlanes – it is the same view as if I would have selected “No Swimlanes”. Could you provide the JQL for the Query of the workaround if one is necessary. As described above my goal is simply to view all stories as swimlanes with their subtasks orderd by their rank – no matter if they actually have a subtask or not. I cannot understand the logic of “Other Issues” when the Stories are grouped.

            Sven Kratzmeier added a comment - The workaround doesn’t seem to work in version 6.2.5.1 anymore. When I change from Stories to Queries there are no swimlanes – it is the same view as if I would have selected “No Swimlanes”. Could you provide the JQL for the Query of the workaround if one is necessary. As described above my goal is simply to view all stories as swimlanes with their subtasks orderd by their rank – no matter if they actually have a subtask or not. I cannot understand the logic of “Other Issues” when the Stories are grouped.

            Thanks Shaun,

            that solves all my problems

            Kindest regards,

            Björn

            Björn Nord added a comment - Thanks Shaun, that solves all my problems Kindest regards, Björn

            Hi Bjorn,

            Agreed this could be useful, for now you might like to try just setting the swimlane configuration from Stories to JQL, all stories and subtasks will then be shown in rank order.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi Bjorn, Agreed this could be useful, for now you might like to try just setting the swimlane configuration from Stories to JQL, all stories and subtasks will then be shown in rank order. Thanks, Shaun

              Unassigned Unassigned
              898471fc2692 Björn Nord
              Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: