Versions Compared

Key

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

...

If the Checklist Text field is populated, but checklist items are not appearing in the Jira UI, then the import did not notify Issue Checklist that an update occurred. In this case, an automation rule can be used to update the issues and trigger Issue Checklist to re-sync with the Checklist text field:

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

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

  3. Go to Project Settings > Automation and click Create rule.

  4. 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 ).

    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}}
      ---
    3. Save and Run the rule.

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

       

...

If both the source and target Jira instances use Issue Checklist, then migrating data may create a second Checklist Text field which is not synced with Issue Checklist installation on the target Jira instance. An automation rule can be used to copy data from the imported Checklist Text field to the original (target) Checklist Text field:

  1. Ensure theSave local checklist items to Jira custom fields global setting is enabled.

  2. Change the name of the un-synced (imported) Checklist Text field so that you can easily distinguish between the two fields. To determine which Checklist Text field is the synced one:

    1. Add one of the fields to the View issue screen.

    2. Open an issue and add a new item to the checklist.

    3. Refresh the issue. If the content of the Checklist Text field updates to include the newly added checklist item, then it’s the field that synced that to Issue Checklist.

  3. Note the custom field IDs of the both the synced Checklist Text field and the renamed Checklist Text field created by the import.

  4. Go to Project Settings > Automation and click Create rule. Create the following 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 ).

    2. Action Edit issues, select Checklist Text as the field to be updated and enter (where 10042 is the custom field ID of the renamed/imported Checklist Text field):

      Code Block
      {{issue.customfield_10042}}

       

    3. Save and Run the rule.

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

    5. You may want to hide or delete the duplicate/imported Checklist Text field.

...