10 / 35 /

75  / 150 / 325 / 480 / 650 / 875 / 950

n/a

customfieldvalue.stringvalue stores ID references to predefined options:

11202
11201
11200

customfield.textvalue stores one JSON field per issue, with direct option values:

[{"id":"Overview Doc Written","type":"done"},{"id":"High Level User Stories Written","type":"done"},{"id":"UX Design Developed","type":"done"},{"id":"Eng Tech Spec Written","type":"todo"},{"id":"Eng t-shirt Size & Quarter Commit","type":"todo"},{"id":"All Sprints Scheduled","type":"todo"}]

customfieldvalue.textvalue stores one JSON field per issue, with direct option values:

[{"description":"Overview Doc Written","checked":true},{"description":"High Level User Stories Written","checked":true},{"description":"UX Design Developed","checked":true},{"description":"Eng Tech Spec Written","checked":false},{"description":"Eng t-shirt Size & Quarter Commit","checked":false},{"description":"All Sprints Scheduled","checked":false},{"description":"All Code Checked In & Tested","checked":false}]

customfieldvalue.textvalue stores JSON records (one per checkbox), referring to a predefined option.

{"checked":false,"name":"","mandatory":true,"rank":5,"optionId":11215,"version":"3.0","id":11215,"statusId":"none"}{"checked":false,"name":"","mandatory":true,"rank":4,"optionId":11214,"version":"3.0","id":11214,"statusId":"none"}{"checked":false,"name":"","mandatory":true,"rank":3,"optionId":11213,"version":"3.0","id":11213,"statusId":"none"}{"checked":true,"name":"","mandatory":true,"rank":2,"optionId":11212,"version":"3.0","id":11212,"statusId":"none"}{"checked":true,"name":"","mandatory":true,"rank":1,"optionId":11211,"version":"3.0","id":11211,"statusId":"none"}{"checked":true,"name":"","mandatory":false,"rank":0,"optionId":11210,"version":"3.0","id":11210,"statusId":"none"}

For per-issue checkboxes, "name" has a value and "optionId" is 0.

• Free, with all the implications for support that entails
• Compares favorably with Kanoah.

• No search.
• The search/list view displays a progress bar rather than attempting to list the checkboxes, which might work well in some scenarios and not in others.
• Support is via a custom JIRA Service Desk instance. While possibly good for privacy-conscious users, it means there is no answers.atlassian.com "knowledge base" to tap into.

• The only viable choice if you need centrally managed task definitions, while still retaining the flexibility of per-issue tasks.
• Has per-item statuses and special formatting of @user mentions and dates.
• Has relevant workflow post-functions and validators.

• Creating a task list is rather an involved process: click on the Todo tab, pick a template and give the new Todo list a name; then Edit the new Todo list and assign a user; at which point you finally get checkboxes.
• Multiple distinct sets of todos per issue.
  • Notifications to watchers, permissions and other fancy features (see docs).

• Support via custom website; no answers.atlassian.com "knowledge base".

Simple Tasklists is interesting, because tasks can be interspersed within a free-form issue description, or added via comments, and are all nicely aggregated by the Task panel. Like in Confluence, tasks can be assigned via @mention reference, and will appear in a user's task tray.

The plugin has some limitations and missed opportunities at present:

• Like all alternatives except Checklists for JIRA, issues do not share task list definitions

• (in practice, this means a {tasklist} expands immediately to a series of {task}s). Each issue's set of tasks varies individually, and changing the templates will only affect new issues.
• There appears to be no search-for-issues-by-task facility (link).
• As there is no specific field to appear in search results. The Description field can do the job, but only if it contains all {task}s, and none were defined in comments.
• The database refers to issue keys (e.g. PRJ-9), which probably will break if projects are renamed.