Deep Clone for Jira can be used for cloning from one Jira Cloud instance to another.
Both instances need to have Deep Clone for Jira installed
The user triggering the clone shall have access to the target instance and the appropriate permissions to create issues
For setting up instance clone, admin permissions are required on both instances
Cloning to another instance is currently only supported in Bulk Clone.
When cloning to another instance, all the regular features of Deep Clone for Jira are supported, with the following exceptions:
Create and confirm cannot be used due to technical limitations, only “Clone Immediately” is available
Issue links that are targeting an issue that is not being cloned to the other instance will be added as “Web Links”
Confluence links will also be added as “Web Links”
When cloning the sprint of an issue, the “Clone Sprint ID” option is not supported, as the sprint does not exist on the target instance
Setting up instance clone
Follow the instructions below to configure instance clone from e.g.
Ensure you have admin permissions in both instances
first-instance.atlassian.net, go to Apps > Manage Apps > Deep Clone > Instance Clone
Click on Add new target instance and enter the complete URL of the target instance i.e.
Generate a binding key
Follow the instructions in What comes next? to finish connecting the two instances. If there is an error while submitting the key on the second instance, please generate another key and closely verify that the provided URL is correct
first-instance.atlassian.netis now able to clone to
second-instance.atlassian.net. The other way around can be setup by clicking on Add as target instance on
second-instance.atlassian.net. Both instances are able to disable this connection at any time
In the Bulk Clone dialog, you can now select Clone to another instance… in the Target Project dropdown to clone from one instance to the other