Merge data from multiple Jira

Merging multiple Jira Cloud instances is usually performed through temporary Jira Server installation. During that process, all issue IDs are changed. 

To make sure the checklist data is imported/merged along with other Jira data, please follow the steps below.

Source Jira Cloud

As a first step, please enable “Save checklist data to Jira custom fields” toggle on all Jira instances where Issue Checklist is installed.

This way, all checklist data will be stored in Jira custom fields and migrated automatically with other Jira data in custom fields.

Destination/merged/final Jira Cloud

Step to take when all data is merged and imported to the destination Jira Cloud instance:

1. Install Issue Checklist

2. New installation of Issue Checklist will create new Checklist Text and Checklist Content YAML fields (you will have duplicate fields with those names as they were also imported from old Jira instance).
   Please find the ID of the old and new custom field named “Checklist Content YAML”

3. Enable “Save checklist data to Jira custom fields”

4. Copy content of the old custom field to the new one for all issues (or just all issues with the non-empty old custom field).
   This step can be done in several ways, e.g.:

   1. through CSV import/export or

   2. using Script Runner.

5. Perform bulk “empty/fake” update to let the Issue Checklist know there is a new value waiting in custom fields to be picked up and synced.
   This step might not be necessary if Jira sends a notification to the Issue Checklist in step #4 (but it depends on the method you choose).