Revyz Command Center for Jira
Revyz Command Center for Jira
Breadcrumbs

Restore Assets Configuration

About this Page

This page is the starting point for managing the transfer or synchronization of Jira Assets configuration data (e.g., schemas, object types, attributes, references, etc.) between Jira environments. It provides two distinct methods for deployment and maintenance of these configurations:

What is the use case?

The primary use of this page is to either Create a complete, fresh copy of Jira Assets configurations to overwrite a target environment, or to Update/synchronize the target by copying only modified configurations.


This feature is applicable to

command Center for jira assets data manager for jira


image-20251125-054522.png
Assets Configurations

What is Restore Assets Configurations?

With this feature, you can replicate assets objects, schemas, and configurations.

Create duplicate copy

  1. Function: Creates a complete and fresh copy of the source Assets configuration.

  2. Impact: This operation is destructive, as it will overwrite the entire existing Assets configuration on the target environment.

Update

  1. Function: Synchronizes the target environment.

  2. Impact: This is a differential update, copying only the new or modified Assets configurations from the source, minimizing disruption and preserving existing, unchanged configurations on the target.

How to Clone Assets Configurations (Create Duplicate Copy)


This feature is applicable to

command Center for jira assets data manager for jira *Advanced

Step 1: Select Source Site Details
image-20251125-151449.png

  1. Define the Source site by selecting the Jira instance that contains the configurations you wish to clone.

  2. Select the Configuration snapshot—a specific point-in-time backup that holds the Assets configurations you want to use.

Step 2: Select Destination Site
image-20251125-152055.png

  1. Select the Destination site where the cloned configurations will be deployed.

  2. Select the Configuration snapshot for the destination site.

  3. Click on “View Object Schemas” to proceed to the comparison step.

Step 3: Select Object Schemas
image-20251125-152635.png

  1. Review the list of Object Schemas available for cloning.

  2. Enter the new name and key for the object schemas on the destination site (if renaming is required).

  3. Click on “Review dependencies”.

Step 4: Review Dependencies
image-20251125-152837.png

  1. Review the list of underlying dependencies (e.g., attributes, references) required by the selected Object Schemas.

  2. Click on “Next”.

Step 6: Restore Assets Objects
image-20251125-152958.png

  1. Determine whether you want to clone the actual Assets data by selecting Yes or No for the question: "Do you want to restore issues?"

  2. Click on “View Summary”.

Step 7: Review Summary
image-20251125-153208.png

  1. Review the complete summary of the clone job, including the selected configurations, dependencies, and chosen action (Create Duplicate Copy).

  2. Click on “Clone” to proceed to the final confirmation.

Step 8: Completion of Cloning
image-20251125-153620.png


  1. A final confirmation modal will appear.

  2. Enter the Captcha code to securely confirm and initiate the configuration replication job.

How to Clone Assets Configurations (Update)

This feature is applicable to

command Center for jira assets data manager for jira


Step 1: Enter Source Details


image-20251125-062042.png


Select the source site and the relevant assets configuration snapshot.

Step 2: Enter the Destination Site Details
image-20251125-062213.png

Select the destination site and enter the assets configuration snapshot.

Step 3: View Object Schemas
image-20251125-062315.png


Compare the object schemas, currently there are no changes in the object status.

Step 4: Assets Configurations


image-20251125-062424.png


image-20251125-064009.png


The "Clone: Assets configurations" grid provides an essential breakdown of the synchronization scope:

  • User Selected Items (55): These are the 55 primary Assets configuration items (e.g., Object Schemas, Object Types) explicitly chosen by the user for migration.

  • Dependencies (1691/1691): These are the 1,691 underlying configuration elements (attributes, references, etc.) that the 55 selected items rely on. The ratio confirms all required dependencies are identified.

  • Columns: Filtering and identification columns include Name, Parent schema, and Parent object type.

The process is ready for the final mapping and execution step.

Step 5: Review Dependencies
image-20251125-064144.png


Select the desired assets configurations and click on “Review Dependencies”. Click on the relevant filters to check the correct object statuses.

Step 6: Select Object Types


image-20251125-065238.png

There are no dependencies detected, hence the “Next” option is disabled.