• 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

            [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 !

            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.

            +1

            Yatish Madhav added a comment - +1

            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

            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.

            +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

            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!

            +1 Would be a great feature to have, as we run multiple sprints in parallel.

            Marilee Bostic added a comment - +1 Would be a great feature to have, as we run multiple sprints in parallel.

            eli added a comment -

            +1 we are currently experiencing the same issue with multiple active sprints.

            eli added a comment - +1 we are currently experiencing the same issue with multiple active sprints.

            +1 and use case: We also run concurrent (actually overlapping) active sprints. BUG 1: The active sprints do not follow the start/end date ordering as described in the documentation (not alpha sort either? Seems random?), and ENHANCEMENT 1: Active sprints cannot be reordered in the backlog view the same way as non-active sprints.

            Deleted Account (Inactive) added a comment - - edited +1 and use case: We also run concurrent (actually overlapping) active sprints. BUG 1: The active sprints do not follow the start/end date ordering as described in the documentation (not alpha sort either? Seems random?), and ENHANCEMENT 1: Active sprints cannot be reordered in the backlog view the same way as non-active sprints.

            jowan added a comment - - edited

            This is very counter intuitive. It is a no-brainer to reorder priorities in on going sprints. Please activate this feature.

            jowan added a comment - - edited This is very counter intuitive. It is a no-brainer to reorder priorities in on going sprints. Please activate this feature.

            The current restriction is pretty bad. Not even sure how it determines the order for these. Doesn't appear to be name or date ranges. 

            Cory Nelson added a comment - The current restriction is pretty bad. Not even sure how it determines the order for these. Doesn't appear to be name or date ranges. 

            +1 upvote.  Ability to order active sprints in any order or at least by start or end date would be very helpful.

            Thuy-Linh Chu added a comment - +1 upvote.  Ability to order active sprints in any order or at least by start or end date would be very helpful.

            Farina BP added a comment -

            +1 We currently have an issue with two started sprints not showing in chronological order so would like to be able to change this.

            Farina BP added a comment - +1 We currently have an issue with two started sprints not showing in chronological order so would like to be able to change this.

            stephen.landry added a comment - - edited

            So, I was looking the new Release notification for 8.12 that was sent out today... and noticed that the User Picker was improved to also include the Avatar. The User Picker suggestion was opened only 6 months ago and only received 3 votes,  The user picker doesn't solve a problem and really doesn't provide any real value. On the other hand, the suggestion for the Sprint board improvement was opened 3 years ago, solves a real problem, improves the usability of Jira, received 25 votes.... and people are still waiting. I don't get it...

            https://jira.atlassian.com/browse/JSWSERVER-20534?filter=98707&jql=project%20%3D%20JSWSERVER%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22User%20Picker%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

             

            stephen.landry added a comment - - edited So, I was looking the new Release notification for 8.12 that was sent out today... and noticed that the User Picker was improved to also include the Avatar. The User Picker suggestion was opened only 6 months ago and only received 3 votes,  The user picker doesn't solve a problem and really doesn't provide any real value. On the other hand, the suggestion for the Sprint board improvement was opened 3 years ago, solves a real problem, improves the usability of Jira, received 25 votes.... and people are still waiting. I don't get it... https://jira.atlassian.com/browse/JSWSERVER-20534?filter=98707&jql=project%20%3D%20JSWSERVER%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22User%20Picker%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC  

            Agreed. This is a no brainer. It doesn't make any sense that Jira has this restriction. It just causes allot of unnecessary headaches and makes JIRA more frustrating to work with. This issue has bitten us in the past and bit us just recently when we added a new project and tried to stream line our process in Jira. Now we have a mess on our hands with no easy way to fix the problem. This should be a simple software change to JIRA, so it's not clear why this has taken 3 years to resolve. 

            stephen.landry added a comment - Agreed. This is a no brainer. It doesn't make any sense that Jira has this restriction. It just causes allot of unnecessary headaches and makes JIRA more frustrating to work with. This issue has bitten us in the past and bit us just recently when we added a new project and tried to stream line our process in Jira. Now we have a mess on our hands with no easy way to fix the problem. This should be a simple software change to JIRA, so it's not clear why this has taken 3 years to resolve. 

            Up-voting on behalf of my PMO.

            Jamie Schork added a comment - Up-voting on behalf of my PMO.

            +1

            Boris Rybalov added a comment - +1

            Up-voting

            Cristina Axentoi added a comment - Up-voting

            OR added a comment -

            Up-voting

             

            OR added a comment - Up-voting  

            Up-voting. Requesting the ability to reorder active sprints. Encountered an issue that caused 2 sprints to be placed out of order, even though there is nothing visible that should suggest why they were placed that way. This causes confusion for the team since the sprints are out of order. 

            mike metzler added a comment - Up-voting. Requesting the ability to reorder active sprints. Encountered an issue that caused 2 sprints to be placed out of order, even though there is nothing visible that should suggest why they were placed that way. This causes confusion for the team since the sprints are out of order. 

            joe owner added a comment -

            Often the Client Changes their mind on what group of work is most important mid sprint, and will have us back burner the current sprint in favor of a new set of work. It would be nice to have the ability to easily communicate (to my team, my leads, and the client) the priority of sprints when that happens. I would recommend using the ordering functionality of Sprints that have not been started as a guide to success . Thanks all.  Also Up-Vote +1

            joe owner added a comment - Often the Client Changes their mind on what group of work is most important mid sprint, and will have us back burner the current sprint in favor of a new set of work. It would be nice to have the ability to easily communicate (to my team, my leads, and the client) the priority of sprints when that happens. I would recommend using the ordering functionality of Sprints that have not been started as a guide to success  . Thanks all.  Also Up-Vote +1

            Up-voting

            Haider Akram added a comment - Up-voting

            Rich Christy (x213) added a comment - - edited

            We also have the need to reorder "multiple sprints".   This is UNBELIEVABLE that something as simple and obvious as this still doesn't work.  Not being able to reorder active multiple sprints makes it confusing for the dev team.  I have to literally name the sprints to imply the correct ordering.  These needs to be voted up

            Rich Christy (x213) added a comment - - edited We also have the need to reorder "multiple sprints".   This is UNBELIEVABLE that something as simple and obvious as this still doesn't work.  Not being able to reorder active multiple sprints makes it confusing for the dev team.  I have to literally name the sprints to imply the correct ordering.  These needs to be voted up

            up-voting this one

            sujoychakraborty93 added a comment - up-voting this one

            They same feature which exists already for planned sprints would be very helpful.

            Simone Kaiser added a comment - They same feature which exists already for planned sprints would be very helpful.

            We have turned on "multiple active sprints" for the board and need to reorder the active sprints too.

            Srinivas Nistala added a comment - We have turned on "multiple active sprints" for the board and need to reorder the active sprints too.

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

                Created:
                Updated: