Deploy Modified Configurations Across Sites

1. Two Atlassian sites: The first site is referred to as https://site-1.atlassian.net and the second as https://site-2.atlassian.net. Learn how to create an Atlassian site

2. The Revyz app must be installed on both newly created Atlassian sites (https://site-1.atlassian.net and https://site-2.atlassian.net). Learn how to install the Revyz app

3. Cross-site connection between the two sites in the Revyz app, which allows cloning from one site to the other. Learn how to configure a cross-site connection

• Create a configuration (screen) on both Atlassian sites—https://site-1.atlassian.net and https://site-2.atlassian.net—with the same name.

  • For clarity, let’s name the screen “Demo screen 1”.

  • Add the following fields to the Demo screen 1:

    • Summary

    • Description

    • Reporter

      

  • Repeat the same steps on the second Atlassian site to ensure both screens are identical.

• Next, take a fresh backup (Backup type: Jira Configurations) on both sites: https://site-1.atlassian.net and https://site-2.atlassian.net. Learn how to trigger a backup

  Important: Proceed only after the backup job completes successfully.

• Modify the Demo screen 1 configuration on https://site-1.atlassian.net by adding a new field—for example, the Assignee field.

  

• Go to the first Atlassian site (https://site-1.atlassian.net).

• Navigate to Apps → Revyz Command Center for Jira app → Core Administration → Deploy Configuration.

• Select the "Deploy Jira configurations" card.

• Source Site Details:

  • Source site: The site containing the updated configuration (https://site-1.atlassian.net).

• Destination Site Details:

  • Destination site: The target site where the modified screen will be cloned (https://site-2.atlassian.net).

Select “current state” under the “Select source configuration state”.

• You’ll be redirected to the Revyz Jobs page, the page will transition from Analysis to Action Required.

  • Once the job status becomes “Action Required” click on Next.

• For more information on how to deploy Jira configurations, visit this page.

• You’ll see either “Map configurations” or “Compare snapshots” button.

  • Map configurations: If there are configurations with the same name on, the app will flag them and display auto-mapped configurations.

  • Review the auto-mapped configurations, then click “Compare snapshots”.

• Configuration listing page

  • Locate the Screens section and expand it.

  • Locate “Demo screen 1” in the list. Its status will appear as “Modified”, indicating differences between the version on the source site and the one on the destination site. Select this screen to proceed.

  • Click “Review dependencies”.

• On the Dependencies page, you’ll see configurations linked to the screen.

  • Since the fields (Summary, Description, Reporter, and Assignee) are associated to the screen, they will appear under dependencies.

  • Change the object status filter to include “No change”.

  • As these fields are already present and identical on both sites, their status will show as “No change”.

  • Click “View summary”.

• Summary page

  • Review the summary and click “Deploy”.

  • (Optional) Add job notes to document the purpose of the job for future reference.

  • Enter the CAPTCHA in the command prompt and click Deploy.

  • You’ll be redirected to the Jobs tab in the Revyz app.

• Click on the Job ID.

• View the job details displayed in the cards. You can download the details by clicking the download icon.

• Go to the second Atlassian site (https://site-2.atlassian.net).

• Navigate to Jira Settings → Issues → Screens.

• Search for “Demo screen” and select it.

• Confirm that the “Assignee” field has been added to the screen.