Default Checklist (template) is applied automatically to all new issues (issue types) created in a project. 

Default Checklist (template) is defined per project and issue type, which means that each project and issue type can have its own default checklist. 


You can apply the template from the Automation rule or REST API too. 



Please note that you cannot combine Default Checklist feature with the "Issue Created" trigger from the Automation plugin. 

The reason is that both solutions depend on Jira "Issue Created" notification, which is sent asynchronously, and we don't know which plugin handles it first. 


"Administer Projects" permission is required to create a default checklist.

Users without required permissions will see "Set default" option disabled with appropriate explanation in a tooltip.

Please note that System Administrators in Jira have access to project administration even if they don't have "Administer Projects" permission. Issue Checklist respects that and allows system administrators to work with all the templates. 

Read more about template permissions.


Please note that cloned checklist takes precedence over the default checklist. It means that for issues cloned with a non-empty checklist, the default template is not applied.


Every Jira workflow contains an "Issue Created" post-function by default. It is required by default checklist to work correctly and you should not remove it. 


Defining a default checklist (template)

In order to create a default checklist (template), please follow the steps: