| Tip |
|---|
Global Checklists are currently in BETA and will be available in Issue Checklist for Jira |
|
Checklist for Jira creates 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.
| Table of Contents | ||||
|---|---|---|---|---|
|
Sample Automation Rules
| Child pages (Children Display) |
|---|
Limitations
The examples on this page refer to Company-managed (Classic) Jira projects. See this page for information about the limitations of using Automation in Team-managed (Next-gen) projects.
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.
Jira Service Management currently includes Automation and Legacy Automation. The examples on this page 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
| 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 | ||||
|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|