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

If you trigger a job, find the job details at Core Administration > Revyz Jobs > Restore and Deploy Jobs to check on its status later. The job may be marked as one of the following statuses: Success, Partial Success, or Error. 

If the job is successful:

Your next action is to go to your destination and verify if the items you selected for restore were successfully restored to the destination site.

If the job is a partial success or error: 

• To understand why it was a partial success or an error, go to the logs.

• If the logs are not clear or you have questions, you can reach out to support.

For more information on Revyz jobs, visit: https://support.revyz.io/revyz-data-manager/restore-jobs

Select the source site and the relevant assets configuration snapshot.

Select the destination site and enter the assets configuration snapshot. Click on View Object Schemas.

1. Identify Missing Schemas: Check the Object Status column to see which Asset schemas exist on your source site but are missing from your destination. Items marked "Not Present on Destination" are those available for cloning.

2. Verify Snapshot Timing: Ensure the Destination Snapshot timestamp is recent. If you have changed your destination settings since that time, run a new backup first to avoid data mismatches or "stale" comparison results.

3. Check for Dependencies: Once you select your schemas, always click Review Dependencies. This ensures that any linked data, like user roles or custom fields, is included so your Assets function correctly immediately after the transfer.

• Compare Configuration Details: Use the Diff view to see a side-by-side comparison of the JSON configuration for a specific schema, including its description, unique key, and name.

• Interpret Color-Coded Changes: Easily identify differences using the color legend: red indicates items present on source but not on destination, yellow highlights modified items found on both sites, and green shows items present only on the destination.

• Review Specific Metadata: Check the line-by-line breakdown to confirm that metadata like the "key" (e.g., SCHEM1001) matches your expectations before finalizing the selection.

1. Bulk Select Schemas: Check the top-level checkbox in the table header to select all visible Object Schema names for cloning or restoration in one action.

2. Execute Dependency Review: Once all desired schemas are selected, click the Review dependencies button to identify any linked Jira configurations. like custom fields or user roles, required for a successful transfer.

• Choose Restoration Scope: Decide whether to include actual Assets Objects along with your selected configurations. Selecting "Yes" clones both the structure and the individual data entries, while "No" clones only the empty configuration shells.

• Understand Selection Impact: Review the information panel to confirm that opting out of object restoration will result in the Assets configuration being cloned without any associated assets objects.

• Finalize Before Summary: After making your choice on whether to restore objects, click the View summary button to see a full overview of your migration plan before execution.

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

1. Confirm Global Selection: Before clicking Restore, verify the Total selected count at the bottom of the screen to ensure it matches your expected volume of configuration data. Click on “Restore”.

Add job notes, if required, and enter the CAPTCHA code to complete the process.

If you trigger a job, find the job details at Core Administration > Revyz Jobs > Restore and Deploy Jobs to check on its status later. The job may be marked as one of the following statuses: Success, Partial Success, or Error. 

If the job is successful:

Your next action is to go to your destination and verify if the items you selected for restore were successfully restored to the destination site.

If the job is a partial success or error: 

• To understand why it was a partial success or an error, go to the logs.

• If the logs are not clear or you have questions, you can reach out to support.

For more information on Revyz jobs, visit: https://support.revyz.io/revyz-data-manager/restore-jobs