Instance Clone

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.

Prerequisites
  • Both instances need to have Deep Clone for Jira installed

  • The account triggering the clone needs to have access to the source and target instance and the appropriate permissions to create work items

  • For the initial set-up of instance clone, admin permissions are required on both instances

Setup instance connection

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 ⚙️ Settings > Marketplace apps > Deep Clone for Jira > Instance Clone

image-20260127-075447.png
  1. Click on Add new target instance and enter the complete URL of the target instance, i.e., https://second-instance.atlassian.net

  2. Generate a binding key

Add new target instance screen
  1. 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

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

Instance URL screen
  1. In the Clone dialog, you can now select Clone to another instance… in the Target Space dropdown to clone from one instance to the other

image-20251223-141627.png

Cloning

Once the connection is set up, you can clone to another instance from the clone dialog of all clone types.

  1. Open the clone dialog depending on your clone type.

How do I open the clone dialog?
Single Clone or Epic Clone / Tree Clone
  1. Navigate to the work item you want to Single Clone.

  2. Click on the top right Actions menu ••• > Deep Clone.

Deep Clone option in the issue actions menu



Navigate to the work item you want to clone.

Click on the top right Actions menu ••• > Deep Clone.

Bulk Clone

There are two ways to open the Bulk Clone dialog:

From search results

  1. Click 🔍 Search > 🔍 View all work items or Filters > 🔍 Search work items.

  2. Filter the work items you want to Bulk Clone as needed.

  3. Open the Apps dropdown menu (top-right) and select Bulk Clone (Deep Clone).

image-20250924-140817.png

From Apps > Deep Clone

  1. Select Apps > Deep Clone for Jira on the Main Sidebar on the left

  2. Click Bulk Clone in the header of Clone Features page.  

  3. Filter the work items you want to bulk clone by selecting a filter or space, or by entering a JQL query.

image-20251223-135408.png
Space Clone

  1. Select Apps > Deep Clone for Jira on the main sidebar on the left

  2. Click Space Clone in the header of Clone Features page.  

image-20251223-140015.png

  1. Select Clone to another instance in the Target space dropdown

For Space Clone

Select your instance in the Target instance dropdown.

image-20251223-141225.png

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

Jira comment

There are additional considerations when cloning across instances:



Read More