Tickbox Checklists for Jira — every checklist feature, half the price
Tagline: Definition of Done, acceptance criteria and release steps as real checklists on the work item — required items, project statuses, linked templates, workflow gates, automation and board-card progress. Free for 10 users, then US$0.60 per user per month.
Getting started
1. Install
Install from the Atlassian Marketplace listing, or in Jira go to Apps → Explore more apps, search for Tickbox Checklists for Jira and choose Get app. You need to be a Jira administrator. Nothing else has to be switched on: the app works as soon as it is installed, and every feature is available on the free tier.
2. Where it appears
What
Where to find it
Checklists on a work item
Open any work item. The Tickbox Checklists panel is in the right-hand context column; click its heading to expand it.
Open any work item and expand the Tickbox Checklists panel.
Choose Add checklist and give it a name, for example Definition of Done.
Type an item and press Enter. Repeat. Use Tab to indent an item into a section heading.
Click the circle beside any item to tick it. Use the item's menu to mark it required, assign it, or give it a due date.
4. Make it repeatable with a template
Go to Project settings → Apps → Tickbox Checklist Templates.
Choose New template, name it, and add the items you want every work item to get.
Under Apply automatically, pick the work item types it should apply to, and whether it applies on create, on a transition, or on update.
Save. Create a new work item of that type and the checklist is already there.
5. Optional: gate a workflow on it
Go to Project settings → Workflows and edit the workflow you want to gate.
Select the transition, choose Validators → Add validator, and pick one of the Tickbox validators, for example Required Checklist Items Complete.
Publish the workflow. The transition is now blocked until the checklist allows it.
If something looks wrong
The panel is not on the work item. It is in the right-hand context column and starts collapsed. If it is still missing, the app may be restricted for that project under Project settings → Apps.
A template did not apply. Templates apply to the work item types and trigger you chose in step 4; check both on the template.
You cannot tick an item. By default Tickbox follows Jira permissions exactly, so you need permission to edit the work item. A project admin can loosen this in the project template settings.
Summary
Tickbox adds a Checklists panel to every Jira work item. Add as many named checklists as you need; mark items required; give them owners, due dates, priorities and detail; and let templates create them automatically. Progress shows in the panel, per section, on board cards through the "Checklist progress" field, in ten JQL fields, on three dashboard gadgets and on your own "My checklist items" page. Five workflow validators can gate a transition; one configurable post-function can change the checklist as part of one.
Everything runs on Atlassian infrastructure. Checklist data is stored on the work item itself as an issue property, so it travels with the item, is indexed for JQL, and is readable and writable by Jira Automation, ScriptRunner or your own tooling through the standard REST API — no custom-field encoding to reverse-engineer.
What you get
Checklists that carry real information. Multiple checklists per item, headings six levels deep with per-section progress, required items, per-item assignee, due date, priority and collapsible detail.
Statuses you name. Beyond open / in progress / done / skipped, a project can define its own — "Blocked", "In review", "Not applicable" — each behaving as one of the four, so progress, gates and reports keep working whatever you call things.
Required means required. A required item can never be skipped. The rule is in the engine, so it holds in the panel, through the REST API, from an automation rule, from a post-function and from a template.
Templates that keep up. Per project or site-wide, grouped into categories, applied by issue type or by advanced rules (on create, transition or update, with conditions on status, type, priority, assignee, labels, components, summary, description or JSM request type). Mark a template linked and later edits reach the checklists already made from it — while never touching an item somebody has reworded, added by hand, worked on or deliberately deleted.
Workflow gates. Validators for "all items complete", "required items complete", "checklist not empty", "this named item is complete" and "this section is complete". Plus one post-function that can complete, reopen, clear or delete a checklist, or apply a template, on a transition — safe to run twice, because Jira does not promise it runs once.
Automation, natively. An "Update checklist" action in the Jira Automation rule builder: add items, complete, reopen, clear, delete, apply a template, set one item's status, or read progress — with typed outputs a later step can branch on.
Turn an item into a sub-task in one click, created as you, carrying its assignee and due date, linked both ways.
See it everywhere. Board cards ("3/7"), JQL, three dashboard gadgets, a personal "My checklist items" page, a read-only JSM portal panel for customers, and a Confluence macro for any page.
Import and export. CSV for templates — lossless, including detail, heading level and priority — CSV export for live checklists, and paste a markdown list straight onto an item.
A change log per item. Who ticked what, when, and what a template or a transition changed. Bounded, append-only, clearable by a project admin.
Permissions you choose. By default the app follows Jira exactly. A project admin can loosen ticking to anyone who can view the item, or tighten structural edits and template management.
Safe by construction. Every edit is validated server-side, every write is made as you so Jira's permissions apply, and every write carries the revision it was based on so two people editing at once never overwrite each other silently.
Runs on Atlassian. No egress, no external storage, no runtime AI call. Scopes: read:jira-work, write:jira-work, manage:jira-configuration (for the workflow rule configuration screens), storage:app.
Pricing
Users
Price
1–10
Free, every feature
11+
US$0.60 per user per month (US$6 per user per year), flat — no tiers, no item or template caps
The incumbents charge US$1.25–1.49 per user per month on their headline tiers and cap their free editions at 5–6 templates and 20–100 items. Tickbox ships the same feature set — and more in several places — for under half the price, with no caps at any size, because the data lives on the work item and the app runs on Atlassian's own infrastructure with none of our own to pay for.
Getting started
Open any work item: the Checklists panel is there.
Project settings → Checklist templates for templates, project statuses, permissions and CSV.
Jira settings → Apps → Checklists — global templates for templates every project can use.
To collect a checklist on a create or transition screen, add the Checklist field to that screen; what is typed becomes real checklist items.
Not included, on purpose
No AI or Rovo template generation: the app makes no runtime LLM call, so nothing of yours is ever sent to a model. Forge is Cloud-only, so there is no Data Center edition, and Atlassian does not render third-party app modules in the Jira mobile apps.
Support
Email support with a one-business-day response. The documentation includes the issue-property JSON schema, so you can read and write checklists from Automation, ScriptRunner or your own tooling.