Imagine being able to use Configuration Manager for Jira, with all its benefits of confident deployments, no data loss, and configuration integrity, but with far greater flexibility? Imagine being able to pick and chose which configuration elements to deploy or rename them on the fly?
Since version 1.0, the team behind Configuration Manager for Jira has taken into account the need for better flexibility when performing various migration or merger initiatives. Often, when Jira admins migrate or merge configurations, they might either encounter conflicting changes or want to modify certain data sets (e.g., permissions, notifications, etc.) on their Jira target instance.
These scenarios pose some serious challenges for Jira admins – if an admin doesn’t want to modify their target system, they’ll need to go back to their source instance and change the configuration in a way that will ensure no modifications will be introduced during the deployment process. For a typical Jira instance, this could mean hundreds of thousands of renames, and as we all know – renaming an object has a lot of hidden risk attached.
Introducing Selective Merge: Greater flexibility with the same data and configuration integrity
The latest feature from Configuration Manager for Jira, Selective merge, resolves these challenges by enabling admins to avoid overwriting configuration elements on target when deploying configuration snapshots and modify objects from a snapshot on the fly while ensuring the integrity of the configuration.
During the Analyze phase of a snapshot deployment, Configuration Manager detects configuration elements which will be modified on the target instance and allows admins to rename the conflicting objects within the snapshot. The Selective merge functionality creates the renamed objects as new elements on the target Jira instance, thus ensuring no data loss and intact configuration integrity.
Configuration Manager’s Selective Merge supports the following use cases:
– Migrations– during migrations when the configuration of the source system must fit the target instance without altering it other than adding new projects.
– Project Templating– when deploying new projects with a new set of schemes/boards instead of modifying matching ones.
– Concurrent Мodifications– when administrators must handle concurrent modifications in development environments and promote them to production instances.
In a nutshell, Configuration Manager’s Selective merge enables admins to confidently conduct their deployments with far better flexibility, without compromising neither their data nor configuration.