Let’s say we have 2 Scrum Teams, Team A and Team B.
Last Sprint had the name of Sprint5. In that Sprint, Team A wasn’t able to complete all the stories, so, by the time we are about to complete Team’s A sprint, we get the warning that those items are going to be moved to the next Sprint. You think:
Of course I want them to be moved to the next Sprint, since we have already made quite a bit of progress on those ones and we wanna complete them in the upcoming Sprint. I’ll press ok!
Boooom. Those items are not moved to Team’s A Sprint6, but in Team’s B Sprint6!
3.1 Move next Sprint up
Before completing the last Sprint (Sprint5), make sure you have moved your new one (Sprint 6), on top of the other Team’s (Team B) new one (Sprint6):
If you ended up in this post, I guess you probably run into some trouble, regarding your Jenkins release job.
So, you have configured a release job that uses the jgitflow-maven-plugin and you get the following error during the build:
[ERROR] Failed to execute goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) on project [project-name]: Execution default-cli of goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start failed: String index out of range: -6 -> [Help 1]
Searching the Jira tickets of the plugin,, I found out that there is a workaround, where you have to add an additional behavior of checkout to specific local branch:
In my case, I just went directly for the Clean before checkout option, (Source Code Management -> Additional Behaviors -> Add):