What field or action keeps a issue from moving to the next Sprint?

[Scott_Harman]

I am several sprints into my project and every time a sprint is completed some of the issues from the previous sprint pop up in the next one. I have done an extensive amount of testing and come up with the "Done" category I assign to my workflow statuses does not stop this carry over. I have previously asked the Atlassian Community board a similar question and was told to have my users click the dropdown on the Complete Sprint dialog box and choose move pending issue to the Backlog. My management wants another way to systematically require these pending issues go to the Backlog and not the next Sprint. Does anyone have another suggestion?

[Jack Brickey · Accepted solution]

@Scott_Harman , i'm not sure I fully understand your question but let me dive in w/ some details that I suspect you already may know.

For issues to be cleanly be denoted as complete during a sprint the issue should be in the right-most column of the scrum board and the Resolution should be set, i.e. not be "unresolved". It is also a good idea to have the Remaining Time set to 0. I use a post function on the transition to Done to set the RE to 0 just in case the user forgets to do so.

When you complete the sprint you should be prompted w/ the screen shown which is where you decide if you are going to move to backlog or the next sprint. So to be clear is this happening? Assuming so are you asking if there is some default that can be set to not prompt but rather just always push to the backlog? Or something else?

I think, but have not tested recently, that if there is no 'next sprint' create at the time of completing the current sprint then issue move to backlog w/o the prompt.