This step imports checklist stored in a Checklist Text custom field to the DB, so checklists become visible in Jira UI.

Migrating data from other/source Jira with External System Import feature creates Checklist Text field which is not linked with Issue Checklist installation on the current/destination Jira. In this case, you end up with two/duplicated Checklist Text fields.

Migrating data from other/source Jira with CSV Import feature appends data to the existing Checklist Text custom field which is linked with Issue Checklist installation on the current/destination Jira. In this case, you end up with a single Checklist Text field.

Prerequisite:

Install Issue Checklist if it is not installed
Enable the "Save checklist data to Jira custom fields" option in Global Setting.

Two (duplicated) Checklist Text fields

Please note the ID of the source Checklist Text field (created by the External System Import) containing the checklist in plain/raw text format
New/current installation of Issue Checklist will create new Checklist Text field (you will have duplicate fields with those names: one imported from the old Jira instance, the other created by new Issue Checklist installation on the current Jira).
Please note the ID of the new custom field named “Checklist Text”
Copy content of the source custom field to the destination 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.
Check your issues and confirm that they contain checklist items and checkboxes.
If the issues don't contain the checklist items, please read below
Troubleshooting
If the checklist text is present in the custom field but does not get through to the UI after the bulk-update (checkboxes are not visible), then the following might be the reason:
- Issues were not updated (please double check if the correct issues were selected to the bulk-update).
- Provided checklist Text is not valid. Please try to fix it as explained below or contact our support for assistance.
  
  Checklist Text can be validated in the following way:
  - add "Checklist Text" field to an Issue Edit screen
  - edit Jira issue and paste checklist content into Checklist Text custom field
  - save Jira issue
  - refresh Jira issue page - checklist UI should contain checkboxes if the correct and non-empty text has been pastedCheck your issues and confirm that they contain checklist items and checkboxes.
    If the issues don't contain the checklist items, please read below

Single Checklist Text fields

Please note the ID of the Checklist Text field containing the checklist in plain/raw text format (after proper CSV import).
If the Checklist Text custom field has proper content (is not empty) but the checklist is not visible as clickable checkboxes, it means that you used the CSV import feature which does not notify apps (including Issue Checklist) about issue updates.
In that case, you need to force an update of the Checklist Text custom field (e.g. by appending a space character at the end or header at the beginning of each affected issue).
There are several ways of doing it. An example:
1. create an Automation rule that:
  - (the trigger) listens for issue update
  - (condition) continues if the label “imported” is applied
  - (action) updates Checklist Text field by appending a space character - see step 5 in the following guide on how to “append” value: Append checklist items on issue transition
2. bulk update imported Jira issues (in Jira Search list) and apply “imported” label - it will trigger the Automation rule defined above
Check your issues and confirm that they contain checklist items and checkboxes.
If the issues don't contain the checklist items, please double check if the Automation rule (or any other process of updating Checklist Text field that you used) was executed correctly and the Checklist Text custom field was updated.

Browser not supported