Team Checklist, Definition of Done & Google Tasks for Jira

Features

Team Checklist gives every Jira issue two checklists, clearly labelled:

A team checklist — shared by everyone who can see the issue, changed by those who may edit it (Jira’s permissions decide). Items with details, due dates and one level of subitems; drag and drop or keyboard to reorder; progress at a glance (“2 of 6 done”); who added and completed each item.
Your own Google Tasks list — “Only you”. Create a list named after the issue in one click, or attach one of yours. Every change is made in your Google Tasks, so the same tasks are on your phone, in Gmail and in Google Calendar, with Google’s due-date reminders.
Templates — copy any of your Google lists (a “Definition of done”, for example) into an issue, or into its team checklist.
In Jira search, boards and Automation — find issues with teamChecklistOpen > 0, teamChecklistComplete = "true", teamChecklistItem ~ "security" or teamChecklistDue < now(); colour board cards and build quick filters with them; use them in Automation rules.
Block a transition until the checklist is done — an optional workflow rule an admin adds to a transition, such as the one into Done.
Links per issue — keep the design, the runbook and the Drive files of an issue in one list.

Definition of Done that Jira enforces

Add the Team checklist is done rule to a workflow transition, and an issue cannot move to Done until every item is checked:

Searchable in JQL

Private by design

The team checklist is stored by Atlassian, in the app’s Forge storage for your site — never on our servers. We have no server at all.
Google access is limited to your Tasks and the connected account’s email and profile; every Google change is made for the person using the app, with their own account.
Your Google tasks become shared only when you choose Share with the team and confirm.

See the privacy policy for exactly what is stored and where.

Why choose Team Checklist for Jira?

The team and the individual, in one panel: the team works on a shared checklist in the issue, while each person keeps their own to-dos for it in Google Tasks.
Your Google Tasks where you already work: the panel reads your list from Google when it opens and on refresh, so changes made on your phone or in Gmail show up in Jira.
Checklists Jira can act on: search, board colours, Automation and workflow rules use the team checklist directly.

Get Started Today

Install Team Checklist for Jira, open any issue and add the first item — the setup guide walks through every tab.

Also tracking due dates across projects? Pair it with Deadline Tracker for Jira to see deadlines alongside your checklists.

Frequently asked questions

Can a Jira issue be blocked from Done until the checklist is complete?

Yes. An admin adds the workflow rule Team checklist is done to a transition, such as the one into Done; Jira then refuses the transition until every item is checked. It works in company- and team-managed projects.

Can I find issues with open checklist items?

Yes. JQL fields such as teamChecklistOpen > 0, teamChecklistComplete and teamChecklistDue work in filters, board card colours, quick filters and Automation rules.

Who sees the team checklist?

Everyone who can see the issue; people who may edit the issue can change it. It is stored by Atlassian in the app's Forge storage, never on Simplify's servers.

What does Google Tasks sync do?

Each person can create or attach their own Google task list for an issue; changes are made in their Google Tasks, so the tasks are also on their phone, in Gmail and in Google Calendar. Only they see it.

Which Google permissions does it ask for?

Only Google Tasks plus the connected account's email and basic profile, to show which account is connected. It cannot read mail, calendar or Drive.