...
On this page:
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
This page explains:
Migration support details for the app content from server/DC to cloud
Differences between the server/DC and cloud version versions of the app
Pre-requisites
Ensure to:
Install the latest version of Clone Plus for Jira and Jira Cloud Migration Assistant (once JCMA supports migration) on on the server/DC instance.
Comment out any custom clone operation(s) from the clone properties file in server/DC, if you do not intend to migrate the respective clone operation(s) to cloud.
Note |
---|
|
Migration process
Install (and configure) Clone Clone Plus for Jira on Jira on your cloud instance.
Install Jira Cloud Migration Assistant on the server/DC instance from which you intend to migrate the Clone Plus for Jira app configurations. (This step is applicable once JCMA supports migration.)
Use System > IMPORT > IMPORT AND EXPORT > Migrate to cloud > Migrate to cloud to navigate to the migration screen where you can migrate global app configurations, Clone Properties file configurations, and/or users and groups, as required. For more information, refer to this page.
Info |
---|
|
...
The following fields are not supported during migration:
username Username or user ID for user fields such as Assigneeas Assignee, Reporter, and and so on
specific Specific components
Versions
Issue security security levels
Status
Labels
specific Specific values in custom in custom fields
entry Entry substitution variable
Epic issue type includes
All the above-mentioned fields for subtask cloning
...
Feature | Server/DC | Cloud | ||
---|---|---|---|---|
Clone behavior configuration | Supports a property file based configuration. | Provides easy to use configuration screen to define clone operations that control the clone behavior. | ||
Custom clone operations | Supports a maximum of 16. | Supports any number of clone operations. | ||
Clone options:
| Supports all the clone options. | Supports all the clone options.
| ||
Mapping fields from original issue to a new value in the target issue conditioned on original issue field values:
| Supports mapping all issue fields. For more information, refer to the mapping keys section in Mapping keys section in the Clone properties page. | Supports mapping all issue fields. | ||
Setting standard and custom fields for subtasks | Supported. | Not supported. | ||
Single clone conditions:
| Supports all single clone conditions | Supports all clone conditions except Roles andProject category. | ||
Bulk clone conditions:
| Supports all bulk clone conditions for Data Center only. | Not supported. | ||
Clone properties:
| Supports all clone properties. | Supports only:
| ||
Post cloning processing | Functions as expected. | Functions as expected. | ||
Bulk Clone | Supported for Data Center only. | Supported. | ||
Localization | Not supported. | Supported in Spanish, French, German, and Italian. | ||
Advanced field type - User Picker (multiple users) | Supported. | Not supported. |
Problem reporting
If you experience any problems or behavior changes that are unexpected, refer to Help and Troubleshooting or open a ticket with us. This helps us identify and prioritize fixes and improvements.