Restore Projects

• Select this option to generate a brand new copy of one or more existing projects, including all associated configurations (e.g., workflows, schemes, field configurations).

• Click "Create new copy" if your goal is to set up a new project that exactly mirrors the configurations of an existing source project.

Select this option to update existing projects by applying configurations that have been previously saved or reused from other projects, ensuring consistency across your Jira instances.

This page is the first step when creating a new copy of a project, and it focuses on specifying the Source site details for the cloning operation.

Key Components

• Breadcrumb Navigation: Indicates the user's path: Revyz Command Center for Jira / Data Security and Compliance / Restore / Projects Clone / Create New Copy.

• Feature Description: A brief explanation of the feature is provided:

  "Project clone allows you to clone selected project along with its configurations from your source site to destination site or self site."

• Source Site Details: This section is used to define the origin of the project and its configurations that will be cloned.

  • Source site *: This required field specifies the Jira instance from which the project configurations will be copied. In the image, the URL https://revyz-qa.atlassian.net is selected. Users can also select "SELF SITE" if cloning within the same instance.

  • Configuration snapshot *: This required field allows the user to select a specific historical snapshot of the configurations to use as the source for the clone. This ensures the clone is based on a verified state of the project configurations. The image shows a snapshot from Wed, 19 Nov 2025 22:00:32 GMT is currently selected.

• Navigation Buttons:

  • Back: To return to the previous "Projects Clone" selection screen (Create new copy or Update).

  • Next: To proceed to the next step in the cloning process, likely the selection of the specific project(s) to clone.

This screen defines the target environment for the "Create New Copy" operation within the Revyz Command Center.

Destination Site Configuration

• Site *: Specifies the target Jira instance (e.g., https://revyz-qa.atlassian.net). The "SELF SITE" option allows cloning within the same instance.

• Configuration Snapshot *: Selects a specific historical backup of the destination site's global configurations (e.g., Thu, 20 Nov 2025 13:04:58 GMT). This snapshot is mandatory for dependency mapping.

This is the central interface for configuring the project clone job, defining target identifiers and assignments for selected source projects.

2. Project Mapping Grid (Clone: Project) Details

The main section is an interactive list used for selection, renaming, and assignment:

• Selection: Checkboxes enable selection; projects M11 and ISPCP.WH are currently marked for cloning.

• Source Identifiers: The Key and Name columns display the original, non-editable identifiers of the source projects.

• Target Configuration:

  • New Key and New Name: These are editable fields where the user sets the unique key and name for the cloned project on the destination site.

  • Project lead and Default assignee: These fields map the corresponding project roles to specific users on the destination system.

• Filtering: Filters are available under the Key and Name columns for efficient project location.

3. User Actions

Buttons above the grid provide key utilities:

• Export metadata: Allows downloading project configuration details.

• Reset filters: Clears active search parameters.

• Reset selection: Deselects all currently chosen projects.

Enter the new key and name and select which projects you wish to clone, click on “Review Dependencies”.

Review the dependencies and click on “Next”

The Restore Issues panel asks: "Do you want to restore issues?*"

• Yes:

  • Choosing Yes (the "Opting in" described on the left) means that the projects will be cloned along with all their associated issues.

  • Result: A brand new copy of the projects, including all the tickets, comments, attachments, etc., as they existed in the Source Snapshot (Wed, 19 Nov 2025 22:00:32 GMT), will be created on the destination site.

• No:

  • Choosing No (the "opting out" described on the left) means the projects will be cloned without any associated issues.

  • Result: Only the configurations (workflows, screens, custom fields, permission schemes, etc.) of the selected projects will be cloned. The new projects created on the destination site will be essentially empty shells, ready for new issue data.

Once you check the summary, click on “clone” to proceed.

This screenshot shows the Final Review and Confirmation step, often displayed as a modal dialog, just before the Revyz project cloning job is initiated. Enter the Captcha code to finish the process.