Use Deep Clone for Jira for cloning work items and spaces from one Jira Cloud instance to another. The Instance Clone feature is available for all clone types (Single Clone, Bulk Clone, Epic/Tree Clone, Space Clone (Project Clone), Post-Function Clone, Presets).
Preparation
If you want to clone between two instances, the first thing you have to do is set up a connection between your instances.
Step by step
Once the connection is set up, you can clone to another instance from the clone dialog of all clone types.
-
Open the clone dialog depending on your clone type.
-
Select Clone to another instance in the Target space dropdown
Done! You have set up your instance clone.
Cloning Reporters, @ Mentions, and Other User Values Between Instances
Deep Clone for Jira is able to clone user values between Jira instances, if the Jira user is available in both instances and connected to the same email address.
What happens if a Jira user is not available in the target instance?
-
If the reporter is not available in the target instance, Deep Clone sets the user who performed the clone as reporter.
-
If the assignee is not available in the target instance, Deep Clone sets the default assignee in the clone.
-
If the commenter is not available as a user, the creator of the comment is “Deep Clone for Jira”. A web-link to the user of the original work item in the source instance is provided, to track who originally created the comment.
-
If the cloned comment contains a @mention to a user who does not exist in the target instance, the mention will be displayed as “unknown user” or “user”.
There are additional considerations when cloning across instances:
-
Request types and work item types need to be available in the target space
-
If the language settings on target and source instance differ, you need to temporarily change the default language of your profile, so languages match.
Read More