Comparison of Server/DC and Cloud features

If you decide to migrate to Cloud, you should be aware of some limitations. Since Atlassian does not allow third-party custom fields to be installed on the Cloud instance, the most obvious difference is that Checklist Cloud is not a custom field. This means that it cannot integrate as tightly with Jira.

Moreover, many features that exist in the on-premise version cannot be implemented yet on Cloud due to a lack of proper APIs.

The table below summarizes the differences between Server and Cloud. A major label marks big differences where Cloud is generally much less powerful than its on-premise counterpart.

Feature

Cloud

Server

Notes

Feature

Cloud

Server

Notes

Access management

 

X

  • Edit roles and other feature flags to control who can edit and complete checklist items do not exist on Cloud.

Assignees

 

X

  • Not currently supported on Cloud, but @mention can be used to simulate this.

Bulk operations (in the checklist)

 

X

  • Not currently supported on Cloud.

Checklist Custom Fields major

 

X

  • On Cloud, this is done through Checklist Definitions. This also implies that Checklists cannot be displayed in Create, Edit or Transition Dialogs.

Checklist Proxy Custom Fields major

 

X

  • Do not exist on Cloud.

Checklist styling major

X

X

  • The styling on Cloud is much more limited than on Server. For example, the following is not possible on Cloud:

    • Change header display

    • Add show more for long checklists

    • Advanced Markdown

Cloning issues

 

X

  • On Cloud, when you clone an issue, Checklist data is not cloned automatically. However, you can easily copy/import the data from the source issue.

Convert items to issues

X

X

  • The latest version on Server has more flexibility.

Default local items

 

X

  • Not currently supported on Cloud.

Descriptions

 

X

  • Not currently supported on Cloud.

Display on Agile cards major

X

X

  • Cloud only supports a predefined text banner, such as “3/4”.

Due dates

 

X

  • Not currently supported on Cloud, but Date Highlighting can be used to simulate this.

Full Markdown editor

 

X

  • Not currently supported on Cloud.

Global items

X

X

  • On Server, disabled global items stay in checklists if they are checked. On Cloud, they are removed from the checklist, whether they are checked or not.

Importing items between checklists

X

 

 

JQL functions major

X

X

  • Server has much more advanced and powerful JQL functions.

  • No re-indexing occurs when global items are modified, which means that an issue needs to be modified for the JQL to register the changes.

Lock On Resolution (to avoid updating global items in closed issues)

X

X

  • This functionality is identical in both Server and Cloud.

Markdown support major

X

X

  • Server supports advanced Markdown.

Priorities

 

X

  • Not currently supported on Cloud.

Scripting and REST APIs

 

X

  • Not currently supported on Cloud.

Section headers

 

X

  • Not currently supported on Cloud.

Statuses major

X

X

  • On Cloud, statuses are global across all checklists. On Server, statuses can be defined at the custom field level.

Templates

 

X

  • Not currently supported on Cloud.

Workflow functions

 

X

  • Not currently supported on Cloud.

Workflow conditions

 

X

  • Not currently supported on Cloud.

Workflow validators major

X

X

  • Unavailable for Cloud Next Gen Projects, and you can only validate that the entire checklist is completed on Cloud.