Via multiple Custom Fields and/or Custom Fields' contexts.

Each Issue can have multiple independent checklists.

Via multiple Custom Fields and/or Custom Fields' contexts.

Individual checklists can be controlled to appear only on specific project and/or issue type.

You can configure the look and feel as well as the features of each checklist separately.

You can search for data targeting a specific checklist.

When there are multiple checklists on a page, checklists can be collapsed to save space.

Can control the visibility of a checklist per project and/or issue type

How many items and characters can be stored in the checklist.

Unlimited number of checklist items.

Unlimited number of checklist items.

Loss of functionality when exceeding 32,768 characters.

Limited to 32,768 characters across all checklists in an issue.

Limited to 500 characters for a checklist item.

Do not allow duplicate item names.

Global Items are items automatically applied to all applicable issues at once. When you add/change/delete global items, the changes are automatically applied to new and existing issues with the checklist.

Checklist items are automatically added to an issue after the issue has been created.

Checklist items are available in the create dialog and can be modified while creating the issue.

Filter out all completed items from the checklists, leaving only incomplete items.

No one can add extra local items besides the default values.

Only possible when a default value is set.

Multiple people working on the same checklist do not overwrite each other’s changes.

Concurrent editing is possible in “Panel” display mode.

Checklists can be locked to prevent edits once an issue is resolved.

Checklist operations can be reviewed at a later time to determine who did what, and when.

All modifications are tracked in the issue history panel along with the issue’s changes.

All modifications are tracked in the issue history panel along with the issue’s changes.

Independent panel showing all checklist’s modification together.

Independent panel showing all checklist’s modification together.

Via proprietary permission page.

Via project permission page.

Via proprietary permission page.

Can only limit editing permission to admin or reporter.

Full English, French and German translations.

Full English and Russian translations. Partial German translations.

Renders a read-only representation of the Checklist in Confluence.

Ability to controls the visibility, appearance and information displayed in the Checklist Header.

Steps required to have the checklist displayed in an issue right after installation.

Since the checklist is a custom field type, the custom field itself must be created, configured and and added to screens before being displayed on an issue (as with any custom field).

Checklist is available in issues right after installing the app.

Checklist is available in issues right after installing the app.

Since the checklist is a custom field type, the custom field itself must be created, configured and and added to screens before being displayed on an issue (as with any custom field).

The entire checklist can be edited via markdown in a single page.

A markdown representation of the entire checklist can be cut and pasted to/from the clipboard.

Can only be cut and pasted inside the text editor.

Can be pasted directly in input field or the text editor.

A markdown representation of the entire checklist can be shared via different text based tools.

Reset the checklist to the same state as it was when the issue was created.

Change the checklist when multiple issues are selected and changed in a bulk operation.

You can do bulk changes by editing a text representation of the checklist.

Items themselves do not support multiline. You can add more lines to an item in the text editor mode. However, the additional lines are added below the item, outside of it.

Does not support advanced Markdown such as emojis and tables.

Allows multiline within a item.

Limited set of markdown syntax available.

Does not follow standard Markdown specifications.

Offers a limited set of markdown syntax in a single line format.

Does not support images inside section heading, only within items.

Description can only be added from the text editor, not directly in the item.

User can collapse or expand the description of all items at once.

Display an icon which can be moused over to display the description.

Items can be marked as mandatory or optional. This can then be used in validating the checklist’s completion.

Each checklist can have its own independent set of statuses.

Statuses can be added, removed, renamed, and reordered.

Default statuses cannot be renamed or deleted.

New statuses can be added and deleted, but not renamed.

Statuses cannot be reordered.

Links status to the checkbox’s state (selecting a status marks the checkbox as checked).

More control over how statuses and checkboxes interact with each other.

Clicking on a checkbox never automatically sets a status.

Clicking on the checkbox will always set the status to Closed and unchecking it will always set the status to Open.

Inverting the checkbox state will always invert the status.

Clicking on a checkbox never automatically sets a status.

Ability to disable item statuses (use checkboxes only).

As an independent field with a calendar popup to select/modify the date.

Inside the item’s text. Calendar popup is triggered by typing //. Once the date has been selected, you cannot modify it from a calendar popup, only by deleting the date and retyping //.

Inside the item’s text. Calendar popup is triggered by typing //. Modify the date by clicking it.

Can set the time as well as the date.

Displays the date in different colors to indicated past, current and future dates.

Cannot be disabled but remains invisible unless a due date is added in the item’s text.

As an independent field with a user selection popup to select/modify the assignee. Popup also contains actions to unassign, or assign to self.

Inside the item’s text. User popup is triggered by typing @ followed by a letter. Once the assignee has been selected, you can only modify it by deleting the assignee and retyping @.

Inside the item’s text. User popup is triggered by typing @ followed with a letter. Once the assignee has been selected, you can only modify it by deleting the assignee and retyping @.

Inside the item’s text. User popup is triggered by typing @ followed with a letter. Once the assignee has been selected, you can only modify it by deleting the assignee and retyping @.

Can be configured to display the avatar, name or both.

Only displays name.

Only displays name.

Mouse over displays user’s information and link to profile.

Clicking on user’s name opens its profile.

Not native to the app but can be achieved via Automation, which gives greater flexibility and control on the notification and the associated message.

Notifications can be disabled. HTML rendering of the items assigned to you.

Cannot be disabled but remains invisible until a mention is added in the item’s text.

Cannot be disabled but remains invisible until a mention is added in the item’s text.

Cannot be disabled but remains invisible until a mention is added in the item’s text.

@ mention users within the item’s text

No logic behind @mention. Purely aesthetic rendering.

Displays a popup to select the user.

Displays a popup to select the user.

Displays a popup to select the user.

Items can be visually regrouped under a section.

All items underneath the section heading can be collapsed to hide/display them.

Ability to recognize an issue key in the item’s text and render a hyperlink.

Renders the link with the issue’s key only.

Renders the link with the issue’s icon, key and name.

Renders the link with the issue’s icon, key and name.

When the checklist is displayed as a panel.

By showing the Issue Create Dialog, more properties can be set during issue creation.

Shows who last checked/unchecked an item without consulting the operation history.

All users can create templates and edit templates they own.

All users can create and edit any project templates.

Administrators can disable the ability to import templates.

Administrators can configure which project roles can create templates from issues.

Administrators can disable templating mechanism for users and project managers by disabling app’s modules.

Administrators can use Default Local Items to import a template directly on the create screen.

Administrators can use a post function to import a template with advanced conditions.

Project managers can use Automation for Jira to import a template with advanced conditions.

Administrators can configure advanced conditions.

Project managers can configure for which issue types the template will automatically be applied to.

Administrators can configure advanced conditions on any template.

Project managers can configure advanced conditions on their project templates.

When a card is selected, users can modify the checklist in the right side panel.

Shows the number of completed items, for example 3/4.

Users can create their own labels using custom text and predefined %progress variables%.

When using JQL operators (OR, AND), the search result will return the issue where the terms were found anywhere in the checklist.

This feature allows users to match multiple terms inside the same checklist item.

Limited to the item name, status and checkbox fields.

When in the search page, the result of the search can be displayed in a “List View” showing multiple fields.

The entire checklist is rendered as in the issue view.

Users can create their own labels using custom text and predefined %progress variables%.

Supports multiple conditions listed below.

Supports “All items checked” and “All mandatory items checked”.

Can be conditionally applied to specific checklists and/or Issue fields (via JQL or other mean)

Can apply to a specific list of checklists, or all.

Can have issue type, label or JQL condition.

Must select which checklist field it applies to.

Supports multiple validators listed below.

Supports “All items checked”

Supports “All items checked” and “All items have a status set”

Supports “All items checked”, “All mandatory items checked”, “All items must have statuses”, “No items must have statuses”.

Can be conditionally applied to specific checklists and/or Issue fields (via JQL or other mean)

Can apply to a specific list of checklists, or all.

Can have issue type, label or JQL condition.

Can apply to a specific checklist, or all.

Must select which checklist field it applies to.

Changes to the template are not kept in sync with the post function.

Modify checklist items:
- Check or uncheck all items.
- Remove or set statuses.

Can be conditionally applied to specific checklists and/or Issue fields (via JQL or other mean)

Extensions loaded inside Automation for Jira which allow users to perform more complex operations.

Natively imports from within the Checklist for Jira app.

Requires outside tools, manual setup and scripting.

Checklist item’s statistics can be displayed inside the gadgets.

Capability to display checklists' summaries inside the gadget.

Can display checklist, checked / total, progress bar and custom labels.

Can only display checklist and checked / total.

Can only display checked / total progress.

Can only display the checklist item names.

Only available in custom field display mode.

Only available in custom field display mode.

Shows a limited number of items to save real estate. Expand to show all items.

Only available in custom field display mode.

Status selector can be move to different positions.

Can be positioned after the checkbox or at the end of the item’s text.

Checklist features can be individually turned ON or OFF to fit specific needs.

Dozens of features can be individually turned ON or OFF.

Can iterate over all items, each item being an object containing different properties (name, completion, status, etc.).

Data is stored in a text format so each item must be parsed individually.

Data is stored in a JSON string and must be parsed.