Deploy Spaces

Click on “Deploy Configurations”

Click on “Deploy Spaces”

The center of the screen presents two interactive cards for managing "Spaces".

1. Select Source: Choose the source site from which the configuration will be deployed.

2. Select Destination: Choose the destination site where the configuration will be applied.

3. Trigger Analysis: Click Next to trigger a "Jira configuration clone" job, which fetches configuration data from both sites.

Select the source configuration state: current or snapshot from earlier backups done.

Selecting the Source Configuration State is essential because it provides version control for your Jira environment, allowing you to choose between the live Current state or a historical Snapshot. This ensures you can either deploy the most recent changes or revert to a previously known stable configuration to fix errors or accidental deletions. By using a snapshot, you can confidently sync environments like Sandboxes and Production based on a specific, validated point in time.

In the Spaces module, you can efficiently manage your Jira Service Management environments by duplicating existing

Structures or auditing current setups. You have the option to create a new copy to quickly replicate configurations for new projects, or use the Update feature to compare and view specific differences within a space's configuration.

Revyz will perform a deep comparison of both sites to identify all configurations and their inter-dependencies. The job status will transition to Analyzing.

1. Verify Sites: Confirm the Source and Destination instances are correctly assigned.

2. Check State: Ensure the Source configuration state (e.g., "Current state") reflects the version you intend to move.

3. Start Analysis: Click Confirm to create a deployment job and begin the automated dependency analysis.

4. Next Step: Wait for the job status to transition to Analyzing before proceeding to the configuration comparison.

Following that, click the Confirm button to proceed with your deployment configuration.

Click on “Confirm” button to proceed with the deployment configuration.

Revyz will perform a deep comparison of both sites to identify all configurations and their inter-dependencies. The job status will transition to Analyzing.

1. Verify Sites: Confirm the Source and Destination instances are correctly assigned.

2. Check State: Ensure the Source configuration state (e.g., "Current state") reflects the version you intend to move.

3. Start Analysis: Click Confirm to create a deployment job and begin the automated dependency analysis.

4. Next Step: Wait for the job status to transition to Analyzing before proceeding to the configuration comparison.

Click on the job id to check the relevant “Project Clone” details.

Once the analysis is marked as Action Required, click the Next button to move into the configuration mapping stage.

In the Spaces section, you can create brand new copies of your existing environments by reusing their current configurations or use the Update tool to compare and view specific differences in a space's setup. Within the Duplicate configurations mapping interface, you can manage how specific data fields, such as hardware types or custom IDs, translate from your source site to your destination. This workflow ensures you have full control over field mapping and can resolve any duplicate dependencies before finalizing your project clone.

In the Spaces module, you can perform a Project Clone to create brand-new copies of existing spaces by reusing their configurations or use the Update tool to compare differences. During the duplication process, you can resolve potential conflicts in the Duplicate configurations mapping view by choosing to map source fields to specific destination IDs or selecting "Don't map field". Finally, you can select specific spaces to deploy and customize their identity on the destination site by defining a New space key, New space name, Space owner, and Default assignee.

In the Spaces module, you can perform a Project Clone to create brand-new copies of existing spaces by reusing their configurations or use the Update tool to compare differences. During the duplication process, you can resolve potential conflicts in the Duplicate configurations mapping view by choosing to map source fields to specific destination IDs or selecting "Don't map field". Finally, you can select specific spaces to deploy and customize their identity on the destination site by defining a New space key, New space name, and Space owner.

In the Review dependencies phase of a project clone, you can identify and manage any linked configurations or assets required for a successful deployment. This step allows you to ensure that all necessary dependencies are accounted for before finalizing the move to your destination site. Once you have reviewed these items, you can proceed to the final summary to deploy your selected spaces.

You can use the Object status filters to pinpoint items not currently present on the destination, ensuring all critical dependencies are included before proceeding. This step gives you granular control over exactly which underlying components are deployed alongside your project data.

Enter the CAPTCHA code to finish the task.

1. On the Spaces update screen, select the Source site* containing the updated configurations you wish to clone.

2. Choose the specific Configuration snapshot* that holds the desired source configuration data.

3. Click Next.

1. Purpose: You select the Site* where the existing projects reside and need to be updated.

2. Snapshot Selection: You must choose a recent Configuration snapshot* from the destination site. Revyz uses this snapshot as a baseline to compare against the source configuration, identifying the specific differences that need to be applied during the update.

3. Action: After selecting the site and an accurate snapshot, you click View spaces to proceed to the comparison screen where you can select the projects to update.

1. The Update Projects screen displays a list of projects from the source snapshot that can be used to update existing projects on the destination site.

2. Use the table filters (e.g., Key, Name, Type) to locate the projects you are interested in.

3. For each project, you can see if it is Present in source snapshot (Yes).

4. Click Diff View next to a project to examine the specific differences between the source configuration and the destination configuration.

Click on View Differences.

The current display of "NO CHANGE" in both sections indicates that the specific project being viewed is currently identical in both the source and destination environments, meaning no configuration updates are necessary for this item.