Checklists for Jira & Confluence
Keep repeatable work visible on Jira issues and Confluence pages.
Repeatable work is easy to miss when it lives in comments or copied page text. Checklists adds structured checklist work to Jira issues and Confluence pages while keeping Atlassian permissions authoritative.
- Acceptance criteria reviewed
- Unit tests green
- Peer review complete
- Docs updated
- Security checklist passedRequired
Illustrative preview · Example data
Important steps disappear inside unstructured work.
Definitions of done, handover steps and review checks are often copied into comments or maintained in a separate document. Items become stale, ownership is unclear and progress is hard to see.
Teams feel the gap whenever a routine process needs consistent steps without moving the work into another system.
Best for
- Delivery teams
- Engineering teams
- Operations teams
- Knowledge managers
Reusable checklists beside the work they govern.
Add checklist items to Jira issues and Confluence pages, use built-in packs, and review progress without leaving Atlassian. Jira also supports saved templates, methodology views and permission-aware administration.
Three steps from setup to result.
Open the issue or page
Add a checklist where the work already lives in Jira or Confluence.
Start from a pack or add items
Use a built-in pack or create the steps needed for this piece of work.
Complete and review
Tick items as work finishes and use the progress summary to see what remains.
What this app helps your team do.
Jira and Confluence surfaces
Structured checklists appear on Jira issues and Confluence pages in one Forge app.
Reusable checklist packs
Built-in packs support repeatable processes without copying lists by hand.
Required items and progress
Mark required work and review completion from the checklist progress summary.
Permission-aware administration
Host-product access remains authoritative for checklist changes and administration.
Limits and requirements, explained upfront.
- Pre-release: the app is not yet publicly installable and features may change before Marketplace launch.
- Jira and Confluence checklists do not synchronize.
- Saved templates and Checklist Assistant are Jira-only.
- Company-managed Jira projects can use hard workflow validation; team-managed projects receive guidance instead.
What setup and ongoing management look like.
Site, project and space controls govern checklist creation, auto-apply, templates, reports and workflow behaviour. Atlassian permissions remain authoritative. Uninstall follows Atlassian Forge's app-data retention lifecycle; current customer documentation records the detailed boundaries.
What the app can access, and why.
Check the app's runtime, permissions, storage and external connections before enabling it. These details are specific to this app.
Checklists runs on Atlassian Forge with zero external network egress; computation and storage stay inside your Atlassian cloud tenant.
- Runs on
- Atlassian Forge; the app runs inside Atlassian's cloud platform.
- Reads
- Jira issue and Confluence page context needed to display and govern checklists.
- Can change
- Checklist records and limited progress summaries; host-product permissions remain authoritative.
- Stores
- Checklist text, item state, assignment identifiers, settings, templates, audit metadata and search summaries.
- Storage location
- Atlassian-hosted Forge storage, with limited Jira entity properties and Confluence content properties for summaries.
- External connections
- None; zero external network egress.
- Data retention
- Forge app data follows Atlassian's uninstall retention lifecycle; some Confluence checklist records remain until uninstall after a page is deleted.
- AI use
- Checklist Assistant uses Atlassian Rovo and the app's permissions; it does not call an external AI service.
Pricing will appear with the marketplace listing.
This app is not yet publicly available. Current pricing and billing terms will appear here after its marketplace listing is live.
Support from the people responsible for the app.
Tell us which app you're using, where the issue occurred, what you expected and what happened instead. We aim to respond within two Australian business days.