Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Clone Issues from Sandbox to Production Using Deep Clone for Jira

If you're looking to clone issues from a Jira Premium sandbox or a Jira instance used for testing to a production instance, or vice versa, using Deep Clone for Jira, the app provides a seamless and efficient solution. This use case is essential for teams who test configurations or workflows before moving them to a live production environment.

Deep Clone is a powerful tool designed to clone issues and entire projects across different Jira instances, making it perfect for migrating from sandbox to production environments.

Step-by-Step Process

1. Install and Configure Deep Clone for Jira

  • First, ensure that the Deep Clone for Jira app is installed on both your sandbox and production Jira instances.
  • Properly configure the permissions to allow cloning between instances. This involves setting up the Instance Clone feature, which lets you specify a target Jira instance where issues or projects will be cloned.

2. Prepare for Cloning

  • Identify the specific issues or projects in the sandbox that you want to transfer.
  • Double-check that the necessary custom fields, users, and other dependencies are available in the target production instance to avoid data mismatches.

3. Cloning Projects or Issues

  • Navigate to the Deep Clone app in the sandbox environment.
  • Choose either Project Clone or Bulk Clone, depending on whether you are cloning entire projects or individual issues.
  • Select the target production instance and configure any additional cloning settings, such as attachments, comments, and field mappings.

4. Monitor the Process

  • Once you initiate the cloning process, Deep Clone allows you to track progress and view error logs if any issues arise during the migration. If the clone job is large, and you want to run it in the background, you can review the Clone History later to ensure all elements have been copied correctly.

5. Post-clone Validation

  • After cloning, validate the data in your production instance to ensure the integrity of the migrated issues or projects. Check that all required fields, attachments, and comments have been accurately replicated.

Benefits

Using Deep Clone for Jira saves time and ensures consistency when transferring issues between environments. Its customizable options allow teams to clone only the necessary data while ensuring that everything is identical between the sandbox and production instances.


This article is based on an article in our documentation.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events