download the new Actual Window Manager 8.15

The moving of projects between Source (Production 1) and Target (Production 2) instances will result in changes in your Target (Production 2) instance. All exceptions and ways to handle them are listed in the Limitations sections of this guide. The majority of the data objects are handled out-of-the-box by the Configuration Manager for Jira. This guide presents how to run a transparent, end-to-end migration with no data loss.

System snapshot– Contains the entire configuration of a single Jira instance (projects, workflows, schemes, screens, etc.).Project snapshot– Contains the configuration of a number of selected projects (with their schemes, workflows, fields, etc.).There are two types of configuration snapshots: Configuration snapshots are created using the Configuration Manager for Jira add-on and represent the state of your Jira configuration objects and their relations to each other at a given point in time.Production 2 (Target): Your live instance where the project(s) should be moved, expecting minimal downtime and well-tested changes.Production 1 (Source): Your live instance where the project(s) originate, expecting minimal downtime and well-tested changes.The staging should be a clone or close replica of the production environment. Staging – A pre-production environment, where the systems administration team can establish exact procedures prior to rollout. For this document, we'll assume the following definitions:ĭevelopment – A free-for-all one or many environments where users can play with cutting-edge or risky changes.

Download the new Actual Window Manager 8.15