Checklist for Jira creates six custom fields which can be used with Jira automation to automatically execute Jira actions (i.e. transition an issue) in response to changes on the checklist; or to automatically add or update a checklist in response to changes on a Jira issue.toc
Sample Automation Rules
| Child pages (Children Display) |
|---|
Limitations
| Anchor | ||
|---|---|---|
|
|
If an automation rule references the Checklist Text field, the Save local checklist data items to Jira custom fields global setting must be enabled for the rule to function. After enabling the Save local checklist items to Jira custom fields setting, the sync may take a few hours up to a full day, to complete, depending on the size of your instance. Please allow adequate time before using the field in automation rules.
Jira Service Management currently includes Automation and Legacy Automation. The examples on this page these pages refer to Automation.
The Default Checklist feature is not compatible with automation rules that use the Issue Created trigger. Both actions depend on Jira’s Issue created notification and an order of operations error may occur.
Copying Checklist Text
| Anchor | ||||
|---|---|---|---|---|
|
| Tip |
|---|
If you need a to reference the text of a checklist in an automation rule, copy the contents of the checklist editor. |
Finding Custom Field IDs
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|