...

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

If you intend to migrate only users and groups from server/DC to cloud, do not select the Clone Plus for Jira app in the migration screen while using JCMA. Keep in mind that not all the mappings are available when the Clone Plus properties file is migrated. This can result in unusable mappings in-app data. For example, project data and configurations are not migrated.
When you migrate clone customizations from:
- The same server instance to that of cloud more than once, the app data is overwritten in the cloud instance after the latest migration.
- Multiple server instances to the same cloud instance, multiple default clone operations (or multiple clone operations with the same name) are shown on cloud. Note that each of such configurations can be unique though the name and description are the same.

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

It is recommended to retain the clone operations (do not edit or delete) on the cloud instance as-is while the migration process in progress. Once the migration is complete, verify if the custom clone operations from the server/DC instance are migrated as expected to the cloud instance before editing or deleting any migrated clone operation on cloud.
Global configuration settings such as analytical data settings from server/DC override the respective settings on cloud.
The Bulk Clone feature is turned ON for all the clone operations once they are migrated to cloud from server.

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

Notes

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

copy attachments
copy watchers
copy worklogs
copy comments
copy subtasks
copy subtask estimates
copy parent reporter
copy parent versions
copy links
copy epic issues
copy epic issue subtasks
copy epic issue subtask estimates

Supports all the clone options

Note
Images or any form of media added to rich text editor issue fields are copied to the cloned issue only if Copy attachments is selected. If not, a broken image is displayed in the respective field of the cloned issue.

Refer to Jira LegacyserverSystem JIRAserverIdkeyJCPP-1332

729d679a-302c-339f-958b-015e107badcd

Mapping fields from original issue to a new value in the target issue conditioned on original issue field values

Set target project
Set target type
Set target component
Set target version
Set link type
Set link direction

Supports mapping all issue fields

For more information, refer to the mapping keys section in Clone properties

Supports

only:

Set target project
Set target type
Set target component
Set target version

For supporting set link type and set link direction, refer to:

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1210

Clone

mapping all issue fields
Setting standard and custom fields for subtasks	Supported	Not supported

Refer to

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1041

Single clone conditions

Projects
Issue types
Status
Roles
Project category

Supports all single clone conditions

Supports all clone conditions except Roles

Refer to

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1295

and Project category.

Bulk clone conditions:

Projects

Supports all bulk clone conditions for Data Center only.

Not supported

Clone properties

fieldExcludes
fieldIncludes
ignoreFields
projectIncludes
issueTypeIncludes
retainCommentsOriginalDate
retainWorklogsOriginalDate
epicIssueTypesIncludes

Supports all clone properties

Supports only:

Ignore fields (Not applicable to subtasks)
Field excludes
Project includes
Issue type includes

For missing clone properties in Cloud, refer to:

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1214

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1212

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1211

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1213

Post cloning processing

Functions as expected

with an exception:When the administrator modifies the default link type name in issue linking settings from Cloners to any other name, no link is created between the source and target issues during cloning

.

Jira LegacyserverSystem JIRAserverId729d679a-302c-339f-958b-015e107badcd

keyJCPP-1308

Bulk Clone

Supported for Data Center only

Not supported

Jira Legacy

server	System JIRA
serverId	729d679a-302c-339f-958b-015e107badcd
key	JCPP-1249

Supported
Localization	Not supported	Supported in Spanish, French, German, and Italian.

Jira LegacyserverSystem JIRAserverId729d679a-302c-339f-958b-015e107badcdkeyJCPP-1980

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.

Versions Compared

Old Version 20

New Version Current

Key

Description

Pre-requisites

Migration process

Limitations

Differences between server/ DC and cloud versions of the app

Problem reporting

Page Comparison

Versions Compared

Old Version 20

New Version Current

Key

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-0">[data-colorid=</span>

<span class="diff-html-added" data-a11y-before="Start of added content" data-a11y-after="End of added content" id="added-diff-6">r1e7kxgj45</span><span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-7">]{color:</span>

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-8">#333333} html[data-color-mode=dark] [data-colorid=</span>

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-63">#333333} html[data-color-mode=dark] [data-colorid=</span>

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-94">#333333} html[data-color-mode=dark] [data-colorid=</span>

Pre-requisites

Migration process

Limitations

Differences between server/ DC and cloud versions of the app

Problem reporting