...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Description
This page explains:
Migration support details for the app content from server/DC to cloud
Differences between the server/DC and cloud version of the app
Pre-requisites
Ensure to:
Install latest version of Clone Plus for Jira and Jira Cloud Migration Assistant (once JCMA supports migration) on the server/DC instance.
Comment out any custom clone operation(s) from theclone 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 Plus for 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 AND EXPORT > 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 tothis page.
| Info |
|---|
|
Limitations
The following fields is are not supported during migration:
username or user ID for user fields such as Assignee, Reporter etc..., Reporter, and so on
specific components
Versions
Issue security levels
Status
Labels
specific values in custom fields
entry substitution variable
Epic issue type includes
All the above mentioned fields for subtask cloning
Differences between server/ DC and cloud versions of the app
The following table lists the differences between server and cloud versions of the app:
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 Clone properties | Supports |
Set target project
Set target type
Set target component
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 and Project 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 open a ticket with us. This helps us identify and prioritize fixes and improvements.