Skip to:

Marketplace

Tickbox Checklists for Jira

works with Jira Cloud

OVERALL RATINGS

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appRequired items, templates that apply themselves, board progress, JQL fields and workflow gates

watch Tickbox Checklists for Jira video

More details

Runs on Atlassian: no external servers, no egress, and no data leaving Atlassian. Checklist data is stored on the work item itself as a Jira issue property, so it travels with the item, is indexed for JQL, and can be read and written by Jira Automation, ScriptRunner or your own tooling through the standard REST API. Every write is made as the signed-in person, so Jira's permissions always apply, and every write carries the revision it was based on so two people editing at once cannot silently overwrite each other. Every feature is included for every customer: there is no edition split and no cap on checklists, items or templates. Setup and configuration guide: https://ethanj2k.github.io/docs/jira-checklists.html#getting-started

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Tickbox Checklists for Jira integrates with your Atlassian app

Version information

Version 4.6.0•for Jira Cloud

Release date
Sep 22nd 2026
Summary
Confluence macro removed; every surface carries the app's own name
Details

The Confluence macro has been removed. A paid-via-Atlassian app may declare compatibility with only one product, so a Jira listing could never advertise the macro - which meant shipping a feature this listing does not mention and support does not cover, and which anyone running Confluence could meet by accident. Nothing in Jira loses a capability: the macro read Jira through the same resolvers the JSM portal panel uses, and the app declared no Confluence scopes. Confluence may return later as its own properly declared listing.

Every surface the app puts into Jira now carries the Tickbox name, so it is identifiable wherever it appears rather than showing a generic title.

The app also now publishes a privacy policy of its own, covering only this app and what it stores, at https://ethanj2k.github.io/docs/privacy-jira-checklists.html - the listing previously pointed at an umbrella policy written for the whole portfolio.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow