- Introduction
- About
- Get started
- Migration to Cloud
- Bundled Fields
- Overview
- Add Bundled Field
- Bundled Fields Configuration
- Format and validation
- Using Bundled Fields
- Advanced settings
- Bundled Fields Searcher
- Java API (ScriptRunner)
- Data Sources
- Email notifications
- Bundled Fields v.6.8.x - 6.9.x
- Bundled Fields v.6.7.x
- Dynamic Forms
- Dynamic Forms
- Supported fields
- Visibility
- Request Types visibility
- Fields visibility
- Customer Portal visibility
- Options visibility
- Requirements visibility
- SLAs visibility
- Java API
- Multilevel Structure
- Configuration
- Using a multilevel structure on the Customer Portal
- User Synchronization
- Organizations and Groups Synchronization
- Issue View
- Issue View
- Add user's IP address post function
- Restart SLA post function
- Update SLA to date post function
- Customer Portal
- Links
- Export list
- Split column
- Request details view
- Additional fields
- Additional options
- Compatibility
- Configuration Manager
Migrating from Server to Cloud
Learn about the differences between Extension for Jira Service Management Server and Cloud
Feature comparison
While Extension for Jira Service Management Server 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 Server | 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 | |
Already on our Roadmap. Coming soon! |
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.
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 Server | 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. |
Migration
At this time it is impossible to migrate data and configurations while migrating from Server to Cloud, as there is no dedicated migration feature for our apps.
External System Import which is a standard Jira feature can be used for the migration. However, the process requires to be performed smoothly that’s why it is recommended to try the import using sample data and test instances.
To perform the migration:
- Access Jira Server > Issue Navigator > Export to CSV and use the option to export filtered list of issues
- Prepare the exported file for the Cloud import by using the official Atlassian documentation.
- Access Jira Cloud and select System > Import and Export > External System Import > CSV import wizard
- Map custom fields to the corresponding Jira custom fields even though dynamic custom fields are not available on Cloud. You can map the fields by e.g. turning a dynamic select into a select list.
Keep in mind that to perform the migration, you need a separate license for the Extension for Jira Service Management.
By importing your Jira Cloud instance from a backup, install this app before performing an import. This way you’ll prevent the system from not seeing the app.
For more information on migrating from Jira Server to Jira Cloud, see the official Atlassian documentation.
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.
