Checklists in Cloud vs. On-Prem

How Checklist Work in On-prem vs Cloud

If you are moving to Cloud, then you’ll be migrating from Checklist for Jira Server/DC to Issue Checklist Pro.  Both apps offer similar functionality, but in some cases achieve that functionality in different ways. This page explains how the two apps work, compares available features/functionality and describes features that will be offered in the upcoming cloud Enterprise edition.

See this page for more information on migrating your checklists from Server/DC to Cloud. If you need assistance migrating to Cloud, please contact our support team.

Checklist for Jira

Checklist for Jira creates new custom field types, allowing you to create a custom field for each checklist you use. This means that you can use your checklists anywhere you can use a Jira field, including on create and transition screens. The checklist fields are indexed and include many indexing functions for advanced JQL searches. Checklist data is stored directly in Jira and will be exported along with other Jira fields.

Each checklist can have multiple contexts that can be assigned to specific projects and issue types. This allows you to create one custom field (for example, DoD) with different checklist items for different projects/issue types.

Checklist for Jira | Enterprise

When Atlassian launched Jira Cloud, they chose to prohibit app developers from creating custom fields types such as those used in Checklist for Jira on-prem. Therefore, Checklist for Jira | Enterprise stores checklist data as text (in an external database) which is then rendered in the checklist UI on the Jira issue. Since Checklist for Jira | Enterprise does not create a custom field type, the checklists have different configuration options than the options available in Checklist for Jira on-prem. The advantages of this approach is that less support is required from the Jira Administrator (by default checklist permissions follow issue permissions: anyone who can edit the issue can create/edit checklists on the issue) and you can create limitless checklists without adding to your custom field count.

Checklist for Jira | Enterprise does create six custom fields (of standard field types) which hold metadata about the checklist.

The other significant difference between Checklist for Jira on-prem and Checklist for Jira | Enterprise is that Checklist for Jira | Enterprise uses Global Checklists instead of Global items.

Global Checklists are:

• Created and managed by Jira Administrators.

• Applicable to multiple projects and issue types (similar to a custom field context).

• Automatically applied when issues in the designated projects/with the designated issue type are created.

• Stored in HeroCoder’s database, not in Jira.

• Live – Similar to Global Items, any changes made to the global template will automatically be applied to all existing issues having the checklist, as well as any new issues that are created with the checklist.

• Used for metadata such as Checklist Complete, Checklist Progress, and Checklist Percent Progress on the Jira issue.

• Not synced with the Checklist Text field. Rather the checklist will be stored separately and linked to the appropriate issues. Only the completion status (status, checked or not checked) of individual checklist items will be stored on the issue.