Instance Clone

Deep Clone for Jira can be used for cloning issues from one Jira Cloud instance to another.

Prerequisites

• 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

Setting up Instance Clone

Follow the instructions below to configure instance clone from e.g. first-instance.atlassian.net to second-instance.atlassian.net:

1. Ensure you have admin permissions in both instances

2. In first-instance.atlassian.net, go to Apps > Manage your Apps > Deep Clone > Instance Clone

3. Click on Add new target instance and enter the complete URL of the target instance, i.e. https://second-instance.atlassian.net

4. Generate a binding key

5. 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

6. The instance first-instance.atlassian.net is 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

7. In the Clone dialog, you can now select Clone to another instance… in the Target Project dropdown to clone from one instance to the other

There are some special considerations when cloning across instances:

• Cloning reporters, @mentions, and other user values between instances

• Workflow and statuses need to be imported before cloning

• Request types and Issue types need to be available in the target project

• Further limitations