| 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. |
...
If you use blocking issue transition for not completed checklist, then:
- Please follow our guide to add new validator.
- Remove the old validator.
...
- 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.
...
| Info |
|---|
Please note, that only one of the new custom fields uses new name, i.e. Checklist Content YAML field (the old one is Checklist Content). Checklist Completed new custom field uses the same name as the old one. Checklist Progress custom field did not change. |
...
- "Checklist Content" custom field.
- "Checklist Completed" custom field (only if its description does not start with "Do not delete")