There are multiple ways you can use Jira checklists. Local checklists allow users to bypass Jira subtasks and create ad-hoc todo lists on Jira issues. Additionally, Checklist for Jira Enterprise provides two powerful features – Global Checklists and Checklist Templates – that make it easy to ensure compliance and standardize processes across Jira projects. Global Checklists and Checklist Templates have some overlapping features, but also some important differences:
Use Case for Jira Global Checklist: Definition of Done
To better understand how you would use these tools, consider the Agile concepts of Definition of Done and Acceptance Criteria. Definition of Done is a standard you want to meet across multiple issues, across all of your development projects. This makes it a perfect case for using a Global Checklist.
Use Case for Jira Checklist Template: Acceptance Criteria
In contrast, items on templates can be modified by users working on the issue. In the example below, an Acceptance Criteria template has been created with a single item that serves as a prompt. Since each story will have different acceptance criteria, the items are blank. The template serves as a place holder to remind users that they need to define acceptance criteria for each story.
The template can be set as a Default template, ensuring that it is automatically added to issues of a given type.
Once the template has been added to an issue, users can define the criteria. In contrast, the only action users can take on the (Global) Definition of Done list is to toggle the status/completion state of item.
Jira Definition of Done & Acceptance Criteria Example
Finally, it’s worth remembering that in addition to Global Checklists and templates, users can also create local checklists on an issue to help them manage their work, without needing Jira subtasks.
You can improve standardization and compliance in your Jira projects today by starting a free trial of Checklist for Jira Enterprise.
