JIRA issues going to backlog instead of next sprint

Question

Hi!

Our issues used to roll into the next sprint when the current sprint is ended. Now, however, they go to the top of the backlog instead of rolling over, and we end up having to search for issues in the prior sprint where resolved is empty in order to bulk-change them to the new sprint.

We don't recall changing anything but ... clearly something did! Any hints are appreciated, thanks!

We're on Server edition 6.4.11.

Thanks!

Antigone K · Answer

Thanks, Arun!

I started with that AAQ thread yesterday, but alas, it doesn't address the fact that sometimes issues roll over into the next sprint and sometimes they don't, which is why I posted this new question.

Arun_Thundyill_Saseendran · Answer

Kindly have a look into this question. I believe it answers your question.

https://answers.atlassian.com/questions/221216/jiraagile-completing-a-sprint-why-do-issues-move-to-backlog-instead-of-the-next-sprint