| Table of Contents |
|---|
How to Prepare for Migration
Checklist for Jira Server/Data Center
Verify the scope of each Checklist Custom Field Context. Ensure that the Context is only marked as “All Projects” for checklists that you truly want to have on all of your Jira issues. (When using checklists on-prem you may have set the Context to “All Projects,” but omitted the Checklist Custom field on screens in certain projects. When migrating to Cloud, this can result in useless data being stored in the database, or unwanted checklists appearing on Jira issues.)
Some items will need to be verified/reconfigured post-migration. Therefore, you may want to prepare an inventory of:
Global items - Once migration is complete, you may want to create Checklist templates that include these items.
Checklist permissions
Checklist conditions, post functions and validators
Default local checklist items
Anywhere you are using checklist custom fields (create and transitions screens, automation rules, board cards, workflows, etc.)
Assigned checklist items - depending on the migration path you used, user IDs may or may not have been mapped from on-prem to cloud. Therefore, once users are set up in Cloud you will need to re-assign checklist items.
Follow the instructions on this page to create the export file.
Issue Checklist Pro
| Note |
|---|
Note that we recommend that you prepare your data first and wait until you are ready to migrate before starting a trail of Issue Checklist for Jira Pro, as the trial is for a limited time. |
Install Issue Checklist for Jira Pro.
Executing the Migration
| Note |
|---|
Note that Jira will not be impacted by the migration. However, there will be some downtime when you will not be able to access your checklist data. |
...
Note that in the Cloud App, global and local items are separated into two different checklists: an issue that had a checklist with both global and local items in the on-prem version will have two different checklists (global and local) in the Cloud version.
Post-migration Configurations
Once the migration is complete:
Navigate to Jira Settings > Apps > Manage Apps and review the following:
Global Settings – Ensure your global settings are properly configured. (If checklists are not shown on the main issue panel, enable the Show Checklist Always setting.)
Permissions – Review checklist permissions.
Statuses – Verify that any custom statuses migrated correctly.
Issue Checklist for Jira Pro creates several custom fields. However, your instance may also still include checklist-type custom fields that migrated from used in your on-prem instance . These fields will no longer be associated with your checklists. Therefore it is recommended that you review are not supported in Jira cloud. If you were using these fields in places other than the issue panel where you were using these fields, and replace them with the new custom fields created by the cloud app:
Automation rules
Board cards
Create and transitions screens
Workflow conditions, post functions, rules and validatorsDefault local checklist items are not supported in cloud. However, you can accomplish the same thing using a default template.
Checklist item assignees – After verifying that all of your users were successfully migrated to cloud, you may need to re-assign checklist items.
(automation rules, board cards, create and transition screens, workflow behaviors, etc.), you will need to replace those custom fields with the custom fields created by Issue Checklist for Jira Pro.
...