Learn about the rules and properties that are migrated during the Configuration Manager integration.
Configuration Manager facilitates the migration of Jira and Extension configurations onto the same or to a different Jira instance.
For this, it uses special snapshots in two categories:
System Configuration snapshot
Project Configuration snapshot
After generating the appropriate snapshot, you can deploy the configuration from the source on the target Jira instance using four deployment modes:
Merge Project - Adds lacking configuration to the one already existing on a given project.
New Project - Mirrors the entire configuration from the existing project and applies it onto a new project.
Merge Configuration - Adds lacking configuration to the one already existing on a target Jira instance.
Restore Configuration - Restores the entire configuration from the file while overwriting the existing one on a target Jira instance.
Below, there are listed the existing rules for the Extension objects, broken down for each type of snapshot.
System Configuration snapshot
Note
Before making the system configuration snapshot, make sure that the Include Global App Data option is checked.
Info
During the migration, Configuration Manager validates the elements that should be transferred to an instance. To check if the migration has completed successfully, look for the Custom configuration data changed by app with key com.intenso.jira.plugins.jsd-extender line in the Deployment Info section.
Look for the appropriate info to ensure the migration is completed successfully
Extension object
Deployment Modes
Merge Configuration
Restore Configuration
Dynamic Forms
If the app's configuration on the target instance is empty then all the options are imported from the snapshot.
If the configuration on the target instance is not empty then the imported options don't overwrite the existing fields' configurations.
If the configuration on the target instance lacks some of the fields' configurations, the imported snapshot adds the previously lacking options to the target instance.
If the app's configuration on the target instance is empty then all the options are restored from the snapshot.
If the app's configuration on the target instance is not empty then all the options are restored from the snapshot, overwriting each field's configuration.
If the configuration on the target instance lacks some of the fields' configurations, the imported snapshot adds the previously lacking options and restores the rest in the target instance.
Visibility
If the configuration on the target instance is empty then all the options are imported from the snapshot.
If the configuration on the target instance is not empty then the imported options don't overwrite the already existing options. The configuration on the target instance remains unchanged.
If the configuration on the target instance lacks some of the options, the imported snapshot fills the previously lacking configurations.
If the app's configuration on the target instance is empty then all the options are restored from the snapshot.
If the app's configuration on the target instance is not empty, then all the imported options are restored from the snapshot and overwritten on the target instance.
If the app's configuration on the target instance lacks some of the options, the imported snapshot adds the previously lacking options and restores the rest in the target instance.
Info
The technical limitations of the Configuration Manager may cause the multiselect fields such as: Request Types groups,Jira groups or Visibility options to not restore properly.
For example, the app may restore only one out of three Jira groups that should’ve been restored. In case of further difficulties, contact the support team.
Project Configuration snapshot
Extension object
Deployment Modes
Merge Project
New Project
Dynamic Forms
If the app's configuration on the target project is empty then all the options are imported from the snapshot.
If the configuration on the target project is not empty then the imported options don't overwrite the existing fields' configurations.
If the target project lacks some of the fields' configurations, the imported snapshot adds the previously lacking options to the target project.
If the app's configuration on the target project is empty then all the fields' configurations are copied from the snapshot.
Visibility
If the configuration on the target project is empty then all the options are imported from the snapshot.
If the configuration on the target project is not empty then the imported options don't overwrite the already existing options. The configuration on the target project remains unchanged.
If the configuration on the target project lacks some of the options, the imported snapshot fills the previously lacking options.
If the app's configuration on the target project is empty then all the Visibility options are copied from the snapshot.
If you can’t find the answer you need in our documentation, raise a support request.
Include as much information as possible to help our support team resolve your issue faster.
