Jira Clones

On this page:


Creating Jira clones for Test and Staging purposes can be accomplished in several different ways:

  1. If the production environment is virtualized, the whole VM guest can be cloned. The challenges here are usually related to storage provisioning.

  2. If the production environment is using docker.

  3. Using the embedded backup/restore Jira function.

  4. Using Configuration Manager for Jira.

The article below describes in details how you can create or refresh the Jira environment with the latest production configuration.

< 5 min

2 Jira Servers* 

System Snapshot

System Restore



*2 Servers are required. Production and the clone system.


You need one paid commercial license for the Production Jira instance and one free developer license for the Jira clone instance.



This use case has two major phases: Install Jira clone server, refresh the Clone configuration with the Production Configuration.

Install Jira Clone Server

Follow the procedure described in Atlassian’s documentation to install Jira.
It is recommended that the version of the Clone server is the same as in production.

Production to Clone

  1. Production: Create a system snapshot, including all filters, agile boards and dashboards.

  2. Clone: Deploy snapshot

    1. Use System Restore deployment mode.

    2. Review the change and impact analysis in the Analyze step of the deployment. Using the restore mode CMJ will update and remove existing configuration so that the resulting system has the exact same configuration as Production and exact same projects.

    3. Declare SUCCESS/FAILURE based on the deployment result.

    4. Start using the clone as Test and Staging server.

Deploying a snapshot in restore mode may lead to deletion of projects including all issues. This change can not be reverted.


Automation of the above steps can be accomplished using the public REST API.