5 types of Jira Checklist Automation (with examples)

[#1]

Checklists provide a simple but powerful way to guide team members through essential steps in a project, while Jira automation takes over repetitive actions. Didit Checklists for Jira integrates into this experience, reducing the effort you take to manually set-up checklists.

In this article, I have compiled five automation rules. They are especially useful for automatically adding checklists, triggering actions as checklists progress, and sending timely alerts—keeping your team on track.

1. Add Checklists When an Issue Transitions to a new Status

Ensure team members follow standard procedures for each status change without needing reminders with this rule. For example, set up a rule to automatically add a QA Testing Checklist whenever the tasks move to the in testing status. Here’s how:

To achieve the opposite effect—where an issue’s status changes once all checklist items are complete—follow this method:

2. Change issue's status when all items in checklist are done

Simplify task handoff and facilitate smooth progression to the next desired step with this automation:

The "Didit checklist completed" field recognizes when a checklist has been fully finished and is an indicator for when the issue transaction action has to be performed.

3. Automatically Trigger Messages Based on Checklist Completion Percentage

Send automated messages when a checklist reaches certain completion thresholds.

For example, when a checklist hits 90% completion, an automatic message in Slack notifies the team that a task is nearly done, allowing them to prepare for the next steps or review any final requirements.

4. Add a comment to the issue when tasks are skipped

Didit’s "skipped tasks" field can be a powerful automation trigger, ensuring tasks aren’t overlooked when steps in a checklist are bypassed. Configure an automation rule to detect when a specific threshold—like more than 5 tasks—is skipped. When triggered, the automation can add a comment or notify the assignee ensuring skipped items receive the necessary follow-up.

You could also choose to transition the issue, edit the issue, or send an email, among many other possible actions.

5. Append a new checklist to an existing checklist

This automation rule is handy when additional checklists are needed after a task progresses to a new status. Watch this video to learn how once a dev team finishes their Definition of Done checklist, a Product Owner can add an acceptance criteria checklist to ensure everything is in order before a release. Watch tutorial

 

---

Didit checklists for Jira makes it easier than ever to set-up these rules with its new Automation Wizard. Reach out to us if you need help setting up more advanced automations in a call.