| Info | ||
|---|---|---|
| ||
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. |
...
The most common custom field usage is blocking issue transition and , 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.
...
- 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.
You might want to consult our documentation related to Recurring Tasks app for more details.
Reading/writing Issue Checklist data through Jira REST API
...
- "Checklist Content" custom field.
- "Checklist Completed" custom field (only if its description does not start with "Do not delete")