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

WhatWhere to find it
Checklists on a work itemOpen any work item. The Tickbox Checklists panel is in the right-hand context column; click its heading to expand it.
Project templatesProject settings → Apps → Tickbox Checklist Templates
Site-wide templatesSettings (cog) → Apps → Tickbox Global Templates
Your own itemsApps → Tickbox Checklists in the top navigation
Dashboard gadgetsEdit a dashboard → Add gadget → search Tickbox

3. Add your first checklist

  1. Open any work item and expand the Tickbox Checklists panel.
  2. Choose Add checklist and give it a name, for example Definition of Done.
  3. Type an item and press Enter. Repeat. Use Tab to indent an item into a section heading.
  4. 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

  1. Go to Project settings → Apps → Tickbox Checklist Templates.
  2. Choose New template, name it, and add the items you want every work item to get.
  3. Under Apply automatically, pick the work item types it should apply to, and whether it applies on create, on a transition, or on update.
  4. Save. Create a new work item of that type and the checklist is already there.

5. Optional: gate a workflow on it

  1. Go to Project settings → Workflows and edit the workflow you want to gate.
  2. Select the transition, choose Validators → Add validator, and pick one of the Tickbox validators, for example Required Checklist Items Complete.
  3. Publish the workflow. The transition is now blocked until the checklist allows it.

If something looks wrong

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

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

  1. Open any work item: the Checklists panel is there.
  2. Project settings → Checklist templates for templates, project statuses, permissions and CSV.
  3. Jira settings → Apps → Checklists — global templates for templates every project can use.
  4. 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.