Incomplete issues moved to backlog instead of the new sprint

[Ikem Abellon]

Hello Atlassian Community,

I would like to ask for your help regarding the Sprint of one of our customers. When they closed the current sprint it had the option to move the 94 incomplete issues to the new sprint - which is the correct behavior.

However the 94 issues where moved to backlog rather than the new sprints. 

Would like to inquire your expertise on why this behavior occurred? The current sprint is running in parallel with other sprints in the project.

Your help is highly appreciated.

Thanks,
Michael

[Benjamin]

HI @Ikem Abellon : In order to select another sprint to move the issues go into. There should be one that hasn't started. I'm not aware of option popping up to send tickets to an actively ongoing sprint when closing a sprint. 

Hope this helps.

[Daniel Ebers]

Hi @Ikem Abellon

just for a short clarification: did you mean they selected "PIP-NSW-Q1_2021" to roll the 94 issues over (which was the initial intentions) but instead and despite displaying the "target" sprint in dropdown those 94 ones were sent to the backlog?

Is this correctly understood?

Regards,
Daniel

[Ikem Abellon]

Hi @Daniel Ebers ,

Yes that is correct. Instead of rolling into "PIP-NSW-Q1_2021" they are rolled into backlog.

Thanks,
Ikem

[Daniel Ebers]

Quite strange behaviour. Do you have the option in this window to select a different sprint also (so it is "highlighted") and then coming back to the desired sprint?
Maybe it is only some thing of browser not focusing the selection right?