Creating Jira clones for Test and Staging purposes can be accomplished in several different ways:
- If the production environment is virtualized, the whole VM guest can be cloned. The challenges here are usually related with the storage provisioning
- If the production environment is using docker
- Using the embedded backup/restore Jira function described here: https://confluence.atlassian.com/adminjiraserver071/establishing-staging-server-environments-for-jira-applications-802592273.html
- Using Configuration Manager for Jira
The article below describes in details how you can create or refresh Jira environment with the latest production configuration.
< 5 min 2 Jira Servers* System Snapshot System Restore Easy Supported
*2 Servers are required. Production and the clone system.
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 here to install Jira: https://confluence.atlassian.com/jira064/installing-jira-720411793.html
It is recommended that the version of the Clone server is the same as in production.
Production to Clone
1. Production: Create system snapshot, include all filters, agile boards and dashboards
2. Clone: Deploy snapshot
Use System Restore deployment mode.
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
Deploying a snapshot in restore mode may lead to deletion of projects including all issues. This change can not be reversed!
Declare SUCCESS/FAILURE - based on the deployment result.
Start using the close as Test and Staging server.
Automation of the above steps can be accomplished using the public REST API.