Skip to main content
Skip table of contents

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

Introduction

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 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 issues from a sandbox instance to a production instance, or vice versa, thanks to its Jira 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 Issues for Cloning

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

  2. Make sure users related to the issues exist in the target instance and project.

Step 3: Initiate the Cloning Process

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

  2. Open the Deep Clone for Jira interface and choose the Clone to another instance option.

  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.

Step 4: Execute the Clone

  1. Review the cloning configuration for accuracy.

  2. Execute the cloning process. Deep Clone for Jira will replicate the selected issues from the sandbox to the specified project in the production instance.

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

Conclusion

Deep Clone for Jira offers a robust and efficient solution to manage the transfer of 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.