Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10941

Sprints sorted randomly in Planning Board

XMLWordPrintable

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

      When an agile board is configured, by query, to display multiple active sprints, the Planning Board shows the sprints in an unknown order. They are not sorted by start or end date, number of stories, number of points or any other metric I could figure out. When a sprint ends and falls off of the board, the order of the remaining sprints sometimes changes - shouldn't they still sort the same relative to each other? IMHO, the sprint ending soonest should be at top going down to the sprint ending the furthest out. Providing a sort drop-down would be awesome.

      This also causes the Sprint Health Gadget to display the wrong sprint when "Next Sprint Due" is selected as the sprint to display. That's why I marked it a Major priority.

            [JSWSERVER-10941] Sprints sorted randomly in Planning Board

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069276 ] New: JAC Suggestion Workflow 3 [ 3659283 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626366 ] New: JAC Suggestion Workflow [ 3069276 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323874 ] New: Confluence Workflow - Public Facing v4 [ 2626366 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043244 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323874 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031354 ] New: JIRA PM Feature Request Workflow v2 [ 2043244 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 794800 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031354 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme New: affects-server fixme
            Michael Tokar made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Link New: This issue is incorporated by GHS-6131 [ GHS-6131 ]

            Michael Tokar added a comment -

            Thank you for reporting this suggestion.

            The order in which future sprints are displayed on Plan Mode is the order they were created in (i.e. their database unique identifier determines the order).

            With the delivery of GHS-6131, you are now able to re-order future sprints as you wish. This ordering will be consistent across any boards that display these sprints.

            Regards,
            JIRA Agile team

            Michael Tokar added a comment - Thank you for reporting this suggestion. The order in which future sprints are displayed on Plan Mode is the order they were created in (i.e. their database unique identifier determines the order). With the delivery of GHS-6131 , you are now able to re-order future sprints as you wish. This ordering will be consistent across any boards that display these sprints. Regards, JIRA Agile team

              tkotecki Tom Kotecki (Inactive)
              87f04c2a4b4a Joe Cross
              Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: