How can I make sprints for different projects independants

[Charles Delaporte]

I have created 2 scrum boards for 2 different projects (A and B). I created first project A and it went already through 19 sprints. Then I created project B and was able to create and start sprint #1.

During a sprint planning session for project A, I closed sprint #19 and I wanted to start a sprint #20. However the option "Start sprint" was not available: this buttons was grey and I had a message "need to close the active sprint before you can start a new sprint"

I closed sprint #1 for project B and only after that I was able to start sprint #20 for project A.

Could you please indicate what I need to do so that I can run sprints independently for each project?

[Ollie Guan]

Hi @Charles Delaporte,

You need to enable functionality “Using Parallel Sprints”in the background configuration

Server:https://confluence.atlassian.com/jirasoftwareserver074/using-parallel-sprints-889531501.html

Cloud:https://confluence.atlassian.com/jirasoftwarecloud/using-parallel-sprints-797737030.html

[Charles Delaporte]

Thanks for your answer Ollie.

Could you please also clarify the following point: in the link that you sent, there is a note:

Completing parallel sprints

When completing an active sprint with incomplete issues, you can't directly move these incomplete issues to another active sprint. You need to move these issues to the backlog first, and then you can add the issues to the active sprint.

Does this means mean that when I will complete sprint 20, I will have to move all incomplete issues to the backlog and only after that I will be able to move them to sprint 21?

[Ollie Guan]

Yes, when you click to complete the sprint, the system will prompt you how many unfinished Issues are and automatically move them back to the Backlog list.

Then you can re-prioritize all Backlogs and determine which Issues need to be placed in the new sprint.

[Charles Delaporte]

I find this pretty annoying. 

This step is not mandatory when using only 1 scrum board: you can move incomplete items directly from the ending sprint to the next sprint

Is there any rational why Jira requires this additional step when using 2 scrum boards?