Restore Assets Configuration

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.

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.

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.

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.

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”.

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

2. Click on “Next”.

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”.

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.

1. A final confirmation modal will appear.

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

Select the source site and the relevant assets configuration snapshot.

Select the destination site and enter the assets configuration snapshot.

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

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.

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

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