Skip to main content
Skip table of contents

How to Clone Projects and Issues From Sandbox to Production Jira Cloud Instances Using Deep Clone For Jira


Deep Clone for Jira is a powerful app designed to streamline the process of cloning issues within Jira. This tool is particularly useful for teams who work in a product sandbox or testing environment and need to transfer issues to a production environment efficiently and accurately. Jira doesn’t include an easy solution for transferring projects or issues from a sandbox instance to the production instance, or vice versa. Manually transferring issues via CSV from the sandbox to production is time-consuming and prone to errors. Acme Corp needs a solution to streamline this process while ensuring data integrity and consistency.

This page outlines a use case scenario where Deep Clone for Jira is employed to clone projects or issues from a sandbox instance to a production instance, or vice versa, thanks to its Instance Clone feature.

Step-by-Step Guide:

Step 1: Install Deep Clone for Jira

  1. Ensure that Deep Clone for Jira is installed on both the sandbox and production instances of Jira.

  2. Set up both instances for Instance Cloning.

  3. Verify that necessary permissions are granted to the relevant users for cloning operations.

Step 2: Prepare Projects and Issues for Cloning

  1. In the sandbox instance, identify the projects and issues that need to be cloned to the production instance.

  2. Make sure users related to the issue and when cloning a project wanted custom fields exist in the target instance.

Step 3 [Optional]: Clone Your Project

  1. Select the projects or issues to be cloned in the sandbox instance.

  2. Open the Deep Clone for Jira app from the Apps dropdown in the Jira navigation and select Project Clone.

  3. Choose your Target instance from the instances you have set up in Step 1.

  4. Select the project you want to clone.

  5. Choose new Project key and Project name.

  6. Check whether all required custom fields are mapped correctly. (Custom fields with identical names will be mapped automatically)

  7. Clone project.

Step 4: Clone Issues

  1. Click Proceed.

  2. Fetch issues of the original project.

  3. Configure the cloning settings:

    1. Select the target project in the production instance

    2. Choose attachments, comments, or any other issue elements that need to be cloned.

  4. Click Start Clone. Deep Clone for Jira will replicate the selected issues from the sandbox to the specified project in the production instance.

  5. You can monitor the cloning progress through the Deep Clone interface, or let the clone run in the background and later check for errors in the Clone History.

Step 5: Verification in Production

  1. Once cloning is complete, verify the cloned projects and issues in the production instance.

  2. Check for data integrity, ensuring all fields, attachments, and links are correctly replicated.

  3. Perform any necessary adjustments or updates to the cloned issues to align them with production standards.

Benefits of Using Deep Clone for Jira in This Scenario

  • Efficiency: Significantly reduces the time and effort required to transfer projects and issues from sandbox to production.

  • Accuracy: Ensures that all relevant data, including attachments and comments, are accurately cloned.

  • Flexibility: Offers customizable cloning options to fit the specific needs of different projects and workflows.

  • Consistency: Maintains data integrity and consistency between the sandbox and production environments.

  • Traceability: Provides a clear record of what was cloned, aiding in tracking and auditing processes.


Deep Clone for Jira offers a robust and efficient solution to manage the transfer of projects and issues from a sandbox to a production environment. By leveraging this tool, your organization can ensure that your issue migration is smooth, accurate, and efficient. This will enhance overall productivity and maintain the integrity of your project management processes.

Contact us if we can help you with your use case!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.