- Bundled Fields
- 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
- Multilevel Structure
- 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
- Request Form
- Additional custom fields
- Fields visibility
- Fields requirements
- Options visibility
- Additional options
- Configuration Manager Compatibility
Migrating from Server to Cloud
Overview of Extension for Jira Service Management Server and Cloud
While Extension for Jira Service Management Server and Cloud offer similar features, they do differ.
|Feature||Extension for Jira Service Management Server||Extension for Jira Service Management Cloud|
|Dynamic Forms||Configured in global 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 are: Select lists, Checkboxes, Radio Buttons, Priority, and Components.||Configured in project settings. On Cloud, relations between fields can be built with Conditions. Additional validation rules can be set using Validators. Configuration resembles request type settings. Fields are displayed on the form directly by our app. Supported fields are: Select lists, Checkboxes, Radio Buttons, Number field, Text field, Labels, Components, Fix version(s), Affect version(s), Date Picker, Date Time Picker.|
|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 have to be added to the Customer form extension section in the project settings.|
The Visibility and User synchronization features available for Server, are not yet available for Cloud, but are on our roadmap.
Important features missing for Cloud are Customer portal visibility and Request types visibility. Currently, there’s no necessary API available to control what groups different request types and the whole portals should be visible to and it is a known limitation.
Keep in mind, that 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. However, External System Import, a standard Jira feature can be used to aid with migration. You can export filtered list of issues using the Export to CSV option in Issue Navigator in Jira Server, prepare the exported file for import, following Atlassian guidelines here, and use System > Import and Export > External System Import > CSV import wizard in Jira Cloud. In the wizard, Jira will ask to map fields and custom fields. Even though dynamic custom fields are not available on Cloud, you can map these custom fields to corresponding Jira custom fields, for example, turning a dynamic select into a select list. As these actions require precision and need to be performed smoothly, we recommend testing the import wizard on sample data and test instances.
Keep in mind, that you will need a separate license for Cloud apps.
For more information on migrating from Jira Server to Jira Cloud, see 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.