Odd default status when moving tickets from old Jira to Next Gen

[Livia Labate]

I set up a new Kanban board in Jira Next Gen to transition my team's work from an old board in vintage Jira.

When I move tickets from the old one to the new one, the import manager always defaults the ticket status to Blocked rather than To Do. As well, the list of status is in a completely random order (see screenshot).

I can't find a reason for that. Our workflow is very basic (To Do, In Progress, Blocked, Review, Done). Changing the workflow doesn't seem to affect this order in the import manager or what the default is. 

Since I'm using the old board as my backlog and moving happens constantly, this is really inconvenient. Any ideas?

[John Funk]

Hi Livia - Welcome to the Atlassian Community!

If you are doing a bulk move, at some point in the process it shows a mapping between statuses that are different in the two workflows. It usually defaults to the first status alphabetically. In this case, that's Blocked. 

Can you describe the exact steps you are doing?