New custom fields
Issue Checklist v1.8.20 introduced new custom fields integration. The fields are now created and managed automatically by Issue Checklist app.
The previous custom fields, created manually by Jira administrators, are now obsolete and no longer synchronized with the Checklist. These fields can be safely removed.
The above means that JQL queries, workflow validators and scripts, that use old custom fields, need to be updated and start using the new fields.
Why new custom fields?
New custom fields are created and managed automatically by Issue Checklist app. There is no more need for confusing and difficult configuration, i.e. creating the fields and adding them to the proper screen.
New custom fields implementation fixes several problems observed with the old custom fields.
Do I need to migrate?
If you see the warning icon on the Jira issue page, as presented on the screenshot below, then migration might be required (the warning icon is displayed if manually created Checklist custom fields are detected in your Jira).
If you don't see the warning icon, then you are OK to skip this migration guide. You might only want to read about profits of using custom fields.
Migration required warning
To remove the warning icon, please ask your Jira administrator to check if migration is required and delete the obsolete custom fields as described below.
Check and migrate old custom fields
The most common custom field usage is blocking issue transition, reading/writing Issue Checklist data through Jira REST API and populating custom fields and checklist through Recurring Tasks app.
Read more below how to migrate both these use cases.
Blocking issue transition
If you use blocking issue transition for not completed checklist, then:
- Please follow our guide to add new validator.
- Remove the old validator.
Recurring Tasks app
If you populate checklist to the issues created by Recurring Tasks app then:
- go to the configuration page of Recurring Tasks,
- find and edit the recurring task definition,
- move checklist YAML data from the Checklist Content field to the Checklist Content YAML field.
- contact our support to confirm the migration is successful
You might want to consult our documentation related to Recurring Tasks app for more details.
Reading/writing Issue Checklist data through Jira REST API
Jira REST API can be used from the terminal/shell command line, scripts, programs or other external tools.
If your team has built that kind of integration with Issue Checklist then please replace the old custom fields with the new fields in the source code of the script/program using the below tips:
Delete old custom fields
New custom fields contain all the checklist data. The old custom fields data is no longer necessary and there is no need to copy the data from the old custom fields to the new custom fields.
New custom fields are easy to distinguish from the old ones by their description. New custom fields description starts with "Do not delete" text:
Please go to "Jira Settings > Issues > Custom fields" and delete following fields if present:
- "Checklist Content" custom field.
- "Checklist Completed" custom field (only if its description does not start with "Do not delete")