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

Allow reordering Active Sprint

XMLWordPrintable

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

      Problem Definition

      Currently, users are allowed to reorder Sprint which is specifically not started. The re-ordering can be done from the Backlog page. When the Sprint is started, the option to re-order will automatically be removed from the Sprint.

      Suggested Solution

      Allow the Active Sprint to be re-ordered similar to the Sprint which is not started.

      Workaround

      None

          Form Name

            [JSWSERVER-16069] Allow reordering Active Sprint

            Othmen added a comment -

            +1

             

            Othmen added a comment - +1  

            Mr. Gray added a comment -

            How in the world can we not reorder active sprint tickets lol. Come on Atlassian.

            Mr. Gray added a comment - How in the world can we not reorder active sprint tickets lol. Come on Atlassian.

            Carl Ross added a comment -

            The order that is available does not make sense to me.

            From top to bottom it is: Backlog, latest created inactive sprint, earliest created inactive sprint, active sprint.

            If these were numbers, then the sequence would be 1, 3+, 3, 2, it should be 1, 2, 3, 3+ to be in a chronological order from top to bottom.

            The view I would like to be able to select is:

            • Bottom - Backlog
            • Next - Active Sprint
            • Next - earliest created inactive sprint that follows the Active Sprint
            • Next - later created inactive sprints
            • Top - latest created inactive sprint

             

            I appreciate that this may not be what others need, but if the Active Sprint was moveable, then this problem is solved for all (unless you want the backlog at the top).

            Carl Ross added a comment - The order that is available does not make sense to me. From top to bottom it is: Backlog, latest created inactive sprint, earliest created inactive sprint, active sprint. If these were numbers, then the sequence would be 1, 3+, 3, 2, it should be 1, 2, 3, 3+ to be in a chronological order from top to bottom. The view I would like to be able to select is: Bottom - Backlog Next - Active Sprint Next - earliest created inactive sprint that follows the Active Sprint Next - later created inactive sprints Top - latest created inactive sprint   I appreciate that this may not be what others need, but if the Active Sprint was moveable, then this problem is solved for all (unless you want the backlog at the top).

            fan fan added a comment -

            +1 Would be a great feature to have !

            fan fan added a comment - +1 Would be a great feature to have !

            Adam Ziecik added a comment -

            It makes the Sprint Dashboard gadgets unable to run on Next Sprint Due (auto) when the wrong active sprint is on the top (first one).  Thus, it is needed to be able to reorder the active sprints.

            Adam Ziecik added a comment - It makes the Sprint Dashboard gadgets unable to run on Next Sprint Due (auto) when the wrong active sprint is on the top (first one).  Thus, it is needed to be able to reorder the active sprints.

            Yatish Madhav added a comment -

            +1

            Yatish Madhav added a comment - +1

            Al Marcucci added a comment -

            Automations takes the first Active Sprint as "Active" which is very restrictive. This solution will help a lot for Sprint management purposes

            Al Marcucci added a comment - Automations takes the first Active Sprint as "Active" which is very restrictive. This solution will help a lot for Sprint management purposes

            Srikanth Ande added a comment -

            Can we get workaorund for this issue,

            Impacting on dashboard view with this reorder of active Sprints.

            Srikanth Ande added a comment - Can we get workaorund for this issue, Impacting on dashboard view with this reorder of active Sprints.

            Javier Rincon added a comment -

            +1
            This is an absolute must. It's hard to understand how such a critical aspect of agile is not implemented. Where can we vote on this to bring it to the top of the list?
            Thank you and thanks for the hard work

            Javier Rincon added a comment - +1 This is an absolute must. It's hard to understand how such a critical aspect of agile is not implemented. Where can we vote on this to bring it to the top of the list? Thank you and thanks for the hard work

            Derek Adkins added a comment -

            And the Dashboard gadgets that run on Next Sprint Due (auto) also pick the first one.  So I need to put the applicable sprint at the top!

            Derek Adkins added a comment - And the Dashboard gadgets that run on Next Sprint Due (auto) also pick the first one.  So I need to put the applicable sprint at the top!

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Votes:
              71 Vote for this issue
              Watchers:
              44 Start watching this issue

                Created:
                Updated: