We have a new documentation site. Please go here to see the latest.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

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

At the end of the merge, you might end up with a temporary/source Jira Cloud site which you want to merge/copy to the destination Jira Cloud. 

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

If you perform single Jira-Jira migration (so issue and project IDs don’t change) our support can move checklist data between instances on a DB level.
Please confirm with Atlassian support if you are qualified (issue IDs stay the same).

Source Jira Cloud

  1. Enable “Save checklist data to Jira custom fields” toggle Jira settings.
    This way, all checklist data will be stored in Jira custom fields and migrated automatically with other Jira data (the initial save might require a few hours if the switch was disabled before).

  2. Export issues from Jira.
    There are several ways to do it (Jira backup-export, CSV, etc.)

Destination/merged/final Jira Cloud

When all Jira data is merged/imported to the destination Jira Cloud instance (most likely using Jira built-in export/import functionality), please take the following steps to import/activate the checklist data:

  1. Import Jira data (it will create checklist custom fields).
    Please note the ID of the Checklist Text field.

  2. Install Issue Checklist

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

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

  5. 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). You can find all issues containing checklist data in old custom fields using simple JQL, e.g.: cf[10159] is not empty (the number in square brackets is the ID of old/imported “Checklist Text” custom field)
    The copy can be performed in several ways, e.g.:

    1. through CSV import/export or

    2. using Script Runner or

    3. Jira built-in automation. 

When completed, all issues having non-empty checklist custom fields should also display a checklist as a list of checkboxes with progress bars, etc.

Templates are not migrated in the process described above and should be added manually.

If your list of templates is very long (e.g. above 50 templates) and you performed single Jira-Jira migration (so project IDs did not change), please contact us for assistance. 

  • No labels