Apps documentation
Extension for Jira Service Management
Cloud Server/Data Center
Extension for Jira Service Management

Cloud

Server/Data Center

Documentation
FAQ
Release notes
Migration path
Integration
Last updated Oct 29, 2024

Migration path

Learn about the Data Center and Cloud hosting options of the app.

Migration process

At this time it’s not possible to migrate your app data and configurations while migrating from Data Center to Cloud, as there is no dedicated migration path for our apps.

Info
  • To learn about migrating your Jira data, see the official Atlassian Cloud migration guide.
  • Note that by using Extension for Jira Service Management Cloud and Extension for Jira Service Management Data Center you need a separate license for both hosting options.

Feature comparison

While Extension for Jira Service Management Data Center and Cloud offer similar features, there are several differences when it comes to their configuration. Learn about how the apps differ by checking the overview tables below.

General feature comparison

Feature Extension for Jira Service Management Data Center Extension for Jira Service Management Cloud
Dynamic Forms
Show Assignee
Show Attachments
Show SLAs
Show Related Issues
Bundled Fields
User Synchronization
Customer Portal Visibility
Request Types Visibility
Fields Visibility
Info

The Customer portal visibility and Request types visibility features are missing for Cloud due to the known limitation: currently there’s no necessary API available to control which groups different request types and portals should be visible to.

Tip

If you wish to use the features related to Customer portal visibility and Request types visibility you can navigate to the Compatibility section and learn more about the Theme Extension app which can be used with Extension for Jira Service Management Cloud.

Detailed feature comparison

Feature Extension for Jira Service Management Data Center Extension for Jira Service Management Cloud
Dynamic Forms Configured in General Settings and Project Settings. Dynamic relations between fields can be set by adding related fields to the root field. Every related field can be marked as Required. All fields have to be added to the proper screen and request type.

Supported fields
Configured in Project Settings. Relations between fields can be built with Conditions. Additional validation rules can be set using Validators. Configuration resembles request type settings. The app enables you to directly display fields on the form.

Supported fields
Show Assignee Configured in General Settings Configured in Request details extension
Show Attachments Configured in General Settings Configured in Request details extension
Show SLAs Configured in Visibility Settings Configured in Request details extension
Show Related Issues Configured in Visibility Settings Configured in Request details extension
Bundled Fields Configured globally Configured globally. In order to work, Bundled Fields should be added to the selected issue types in Issue view extension section.
Fields Visibility Configured in Visibility Settings Configured in Customer form extension. By configuring conditions for selected fields you can define whether a field is displayed in a request form based on user input in previous fields of the same request form.
Need help?

If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.