Uncomplete issues are moving to sprint=None when completing a sprint

Question

Hi all,
When trying to complete a sprint, we are getting an error message that due to some workflow problems, some not-done tickets can't move to next sprint. When approving, theyr'e moving to sprint = none, which creates a big mess.
Thanks for your help

Liam Maron · Answer

Attaching our main new workflow (The Ready for release + Pending QA ones are new). The status of each ticket is different, some new and some old. The statuses are mapped exactly by the workflow (Board built in the next way: TO DO - IN PROG - PENDING QA - READY FOR RELEASE - DONE).
Not sure about the type of the project.

No matter the state and status of the ticket - it won't move to the wanted sprint, even if you ask the incomplete tickets to move - it automatically moves to sprint=none.

Jack Brickey · Answer

I would need further information to really have a clue as to what to look at next. I would need to look at the workflow to understand what statuses you added. I would also look at the status of the undone issues to see if they are in these new statuses or old statuses. And it would be good to know how your statuses are mapped on your board. Again is this a CMP or TMP project?

Liam Maron · Answer

No, the scrum boards only manages one project in it. We added some new states in our workflows.
The only tickets that do move to the next sprint are the ones we move manually, the problem is general to all tickets that are left and not done.