Versions Compared

Old Version 4

changes.mady.by.user Jennifer Choban

Saved on

compared with

New Version 5

changes.mady.by.user Jennifer Choban

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

Tip

Global Checklists are currently in BETA and will be available in Issue Checklist for Jira

Status
colourBlue
titleenterprise
once released. Contact our support team if you currently use Issue Checklist for Jira
Status
colourPurple
titlePRO
would like to participate in the Beta.

Table of Contents

Importing Checklists Between Jira Cloud Instances

Tip

You may be able to performa a single Jira-Jira migration, so issue and project IDs do not change. Please confirm with Atlassian support if your instance is qualified (if issue IDs will stay the same). Then contact our support team to have the checklist data moved between instances on a database level.

Info

If your instance does not include JSM or Team-managed/Next-gen projects, you may want to use o use Atlassian’s Cloud Migration tool, currently in Beta, as described here, as an alternative to the instructions on this page.

Templatesnote
Note

Limitations

  • This process only works with Company-managed (Classic) Jira projects.

  • If you are using Checklist for Jira

    Status
    colourBlue
    titleENTERPRISE
    , note that this process cannot import Global Checklists. Global Checklists are not saved to the Checklist Text custom field and therefore will not be imported with the issues.

  • Templates are not migrated in the process described here and will have to be added manually. If you have a large number of templates and are performing a single Jira-Jira migration (so project IDs did not change), please contact us for assistance. 

  • Merging Multiple Jira

Instances
Merging multiple Jira

  • Cloud instances is often performed by temporarily moving all issues to a server instance, in which case all issue IDs will be changed. Follow the process below to ensure that checklist data is preserved/merged into the new destination instance.

Source Jira Cloud Instance

  1. Enable the Save local checklist data items to Jira custom fields global setting. This will ensure that all checklist data will be stored in Jira custom fields and migrated automatically with the other Jira data. Note that the initial save might require a few hours if the setting was previously disabled.

  2. Export the issues from Jira to a CSV file using the Backup Jiramethod. Checklist data will be preserved in the Checklist Text field.

...

  1. Install Issue Checklist if it is not already installed.

  2. Ensure that the Save local checklist data items to Jira custom fields global setting is enabled.

  3. Find and note the custom field ID of the Checklist Text field.

  4. Import the Jira data using the External System Import wizard. This will create checklist custom fields. On the Fields page, select Checklist Text as the corresponding Jira Field for the Checklist Text field in the CSV file, but leave the Map field value checkbox unchecked. This will ensure that to the field values are imported exactly as stored in CSV file.

  5. The Checklist Text field will now be populated with data from the import. However, an automation rule needs to be run in order to re-sync the Checklist Text field with the UI. Go to Project Settings > Automation and click Create rule.

  6. Create an automation rule:

    1. Trigger: Select Scheduled.(The scheduled time does not matter – the rule will be manually ran once and then disabled.) Check the Run a JQL search and execute actions for each issue in the query checkbox and enter an expression that returns the imported issues (ex: project = AK AND key > AK-10 AND key < AK-24 ).

      Image Added

    2. Action – Edit issues, select Checklist Text as the field to be updated and enter (where 10039 is the custom field ID of the Checklist Text field.

      Code Block
      {{issue.customfield_10039}}
---
      Image Added

    3. Save and Run the rule.

    4. After confirming that the issues were updated, disable the rule.