Workflow Scheme Migration

Owned by Rosen Marinkov
Last updated: Sept 19, 2023 by Stanley Neychev
2 min read

When the snapshot you are deploying includes:

  • changes in an active workflow scheme,

  • changes in a project(s) - workflow scheme association, or

  • changes in an active workflow,

an issue status migration might be required. The migration will ensure that the status of each issue in the affected projects is valid. Which statuses are valid for an issue is defined by its workflow. This means that when changing a workflow, you may need to tell Configuration Manager for Jira the status of specific issues after the change.

The screen for specifying the new status is the same as the native screen in Jira.

Duration of a workflow scheme migration
Workflow scheme migrations may slow down the deployment process significantly. The duration depends on the number of issues that are used by the changed workflow(s).
A rough guide: the migration of 200 000 issues takes about an hour.

How to ensurе the consistent state of all issues after a workflow scheme migration?

Follow the recommendations below to avoid any inconsistencies in your issues' data after a workflow scheme migration.

  • Avoid creating new issues in the affected project during the deployment process.

  • Run Jira’s Database Integrity Checker before deploying changes that require a workflow scheme migration.

  • Run Jira’s Database Integrity Checker after deploying changes that require a workflow scheme migration. This will help you catch and fix any issues in an inconsistent state that might have passed during the deploy without throwing an error.