Summary

The migration of a workflow scheme is blocked with a message "Migration in progress". This happens after a workflow migration attempt and may last for a few minutes to hours.

Environment

Jira Core 7.x and 8.x

Jira Software 7.x and 8.x

Diagnosis

1. A message "Migration in progress" is presented when browsing the workflow scheme.
2. The atlassian-jira.log is updated with messages containing "Verifying issues can be moved to another workflow for project".

The process might be stuck or still running in he background. Monitor the log for the message and see if keeps cycling through each project:

$ grep "Verifying issues can be moved to another workflow for project" $JIRA-HOME/log/atlassian-jira.log

If the process' still running, it should output lines like these:

2021-04-06 10:37:24,179-0300 JiraTaskExecutionThread-1 INFO admin 632x24156x1 sessionid 127.0.0.1 /secure/project/SelectProjectWorkflowSchemeStep2.jspa [c.a.j.workflow.migration.ProjectMigrator] Verifying issues can be moved to another workflow for project 'PROJECT A'.
2021-04-06 10:37:27,757-0300 JiraTaskExecutionThread-1 INFO admin 632x24156x1 sessionid 127.0.0.1 /secure/project/SelectProjectWorkflowSchemeStep2.jspa [c.a.j.workflow.migration.ProjectMigrator] Verifying issues can be moved to another workflow for project 'PROJECT B'.
2021-04-06 10:37:31,463-0300 JiraTaskExecutionThread-1 INFO admin 632x24156x1 sessionid 127.0.0.1 /secure/project/SelectProjectWorkflowSchemeStep2.jspa [c.a.j.workflow.migration.ProjectMigrator] Verifying issues can be moved to another workflow for project 'PROJECT C'.

Cause

The switching of workflow scheme that's used by many projects or in use by many issues is costly, and may take much more time than expected. This may lead to an impression the feature's blocked, or it may indeed had failed and left the lock in the application cache.

Solution

If still running

If the log's still presenting the "Verifying issues can be moved to another workflow..." message, simply wait for the process to end. It may take some hours depending on the number of affected issues and application load.

If not running

If the log isn't printing such messages for a while, the process might've failed and didn't release the lock. Jira needs to be restarted so the lock will be released and the migration's acknowledged as completed or can be tried again.