nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changing the order of unstarted Sprints

KevinB

In Plan, we organized by creating several future Sprints. We tried to move one to the top of the list.

It seems like the top one is the ONLY one that has the start controls?

How do you move around Sprints?

Bonus points for what the control with the two horizontal lines at bottom of each sprint does.

Thanks

Accepted answers

Ronny Katzenberger

Hi Kevin, there is no way to reorder these future sprints. I would recommend renaming those sprints and "reorder" them that way. To move the assigned stories around, I would select all the stories you want to move and then right-click and "Send to SPRINTNAME" The double horizontal line are your grabber to pull down the sprint scope. Meaning that you can easily add stories from below this sprint into the sprint (pull down) or move stories out of the sprint and into the next sprint (pull up). Hope this helps. Best, Ronny

All comments

Ronny Katzenberger

RicardoA_8cz081

Hi Ronny

As you can see in the official documentation:

Enabling Labs features

To switch 'Labs' on:

Log in as a user with the 'JIRA Administrators' global permission.

Select JIRA Administration from the top bar, then select Add-ons > GreenHopper.

OR, if you are using JIRA 6.0 or later, click the 'cog' icon in the top bar, select Add-ons, then scroll down the page to the GreenHopper section.

Under GreenHopper Labs, select the features that are of interest to you:

Parallel Sprints

Analytics

Parallel Sprints

Turn on Parallel Sprints to enable multiple active, parallel sprints. For example, if you have two teams working from the same backlog, each team can now work on their own sprint.

Please note the following caveats with this simple approach:

The Velocity Chart will not show the velocity per team.

The current implementation assumes that the teams perform estimation identically, which is unlikely in practice.

Please note that this feature is still undergoing development and may change from its current implementation.