I don't think this answer does the question justice or is answered in an unbiased way.
What you are facing is mainly a team/structural issue. It is not unusual to create sprints in advance, it is unusual to have to replan every sprint every time due to "happening stuff" and still believing that sprints can be "planned well in advance". It makes no sense and creates a wrong picture of what the team actually can achieve. Noone wins: Management gets upset because promised features are pushed back, the team gets demoralised because planned work keeps being pushed back (equalling absolutely wasted time spent in planning!).
The correct answer to your question is:
To accomplish this you may have to create the sprint, then drag the sprint 3 issues to sprint 4, then sprint 2 issues to sprint 3; then you'd be able to move what you want from sprint 1 to sprint 2. Does that help? It's easy enough to move issues between sprints from the Agile board.
I agree with you on that point. We faced this problem when we needed to create a new sprint after the running one as a new project came inattended. We had to move every stories to the next sprint and finally put the stories in the first one. You might say this should not happen all the time but when it happens, it's quiet a mess.
Maybe you are planning too many sprints ahead in this case. If you continuously see a need for putting sprints in the middle due to unfinished work or "stuff" happening this is a sign of process (read: your team has work related issues) related issues, not (solely) a tool (Jira Agile) issue.
As Shari wrote it is really trivial to move issues. I won't defend the tool as people should always be over the tools, but it is also healthy to take a step back and actually look at what the people are doing:
Getting disturbed? Comitting to too much (always!)? Getting overruled by others than the PO? Not estimating consistently? Ignoring velocity for commitment?
I have experienced all of the above with my team and all of it resulted in sprint replanning. My personal take on this is that if you start planning more than maybe 2 sprints ahead you are asked/ing for waterfall-using-scrum, not Agile Scrum.
It is a mess, it takes time and hence it can be used openly for informing about structural/company/team issues on the project... And make changes!
Actually you can start more than one sprint at time, but this is currently still in Labs (which means is not yet supported by Atlassian and we may not be able to assist you with problems with this specific feature).
This way you will be able to have more than one sprint at time. You can check this documentation:
Hope it helps,
I have three sprints in my project, sprint 1, sprint 2, sprint 3 and a Backlog.
There is no sprint in progress.
There is too much work in sprint 1. I want to add sprint 1a between sprint 1 and sprint 2 and move tasks from sprint 1 to sprint 1a.
If I use the "create sprint" button, a sprint is created after sprint 3, which isn't what I want.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs