How to skip global configurations while deploying with Configuration Manager

Summary

When migrating project or system configurations using Configuration Manager for Jira (CMJ), users often want to exclude specific global elements (like workflows or automation rules) to avoid overwriting more up-to-date configurations on the destination instance.

This article explains how CMJ handles shared configurations and provides workarounds to prevent overwriting existing objects, since CMJ currently lacks a native "exclude" feature for structural dependencies within a snapshot.

Use Case 1: Preventing overwrites of existing configurations

A user wants to migrate a project configuration from a Development instance to Production, but wants to ensure that specific workflows or shared schemes already present on the destination instance are not overwritten, especially if the destination versions are more up-to-date.

Cause

CMJ is designed to perform structural integrity checks. If a project references a workflow, custom field, or scheme, CMJ includes that object in the snapshot to ensure the project remains functional on the destination instance. If an object with the same name exists on the destination, CMJ's comparison logic (during the Analyze phase) will typically propose an update/overwrite if the contents differ.

Solution / Workaround

While you cannot manually "uncheck" a workflow or field that is a structural dependency of the project you are migrating, you can manage how CMJ handles them using the following methods:

Method A: Unique Naming (Safe Overwrite Prevention)

To ensure CMJ creates a new object instead of overwriting an existing one:

1. On the source instance, rename the configuration element (e.g., rename "Standard Workflow" to "Standard Workflow - V2").

2. Update the project/scheme to use this new version.

3. Create a new snapshot.

4. During deployment, CMJ will see "Standard Workflow - V2" as a new object and will not touch the original "Standard Workflow" on the destination instance.

Method B: Use the Analyze Phase

Before clicking "Deploy":

1. Review the Analyze Results page.

2. CMJ will list all objects as Add or Modify.

3. If you see a shared global configuration marked as Modify that you do not want to change, you must modify the source snapshot or the destination instance to match before proceeding, or accept that CMJ will align the destination with the snapshot's version.

Use Case 2: Excluding Global Automation Rules

A user wants to migrate a project while avoiding "polluting" the destination environment with global automation rules included in the snapshot.

Solution

To skip global Automation rules, just uncheck the Include Global Automation Rules.

Use Case 3: Excluding Apps or App Data

A user wants to exclude all data related to a specific app from a system or project snapshot.

Solution

1. During the Create Snapshot wizard, navigate to the Select Apps page.

2. You can choose to include or exclude entire apps by checking or unchecking the boxes next to the app names.

3. For precise control, expand the app entry to select individual configuration elements while creating snapshot and choosing apps
   
   

   Open

   

Important Recommendations

• Integrity Check: Always run the Integrity Check on both the source and destination instances before creating or deploying snapshots. Resolve all reported errors to ensure a smooth migration.

• Single Project Snapshots: For more information on how CMJ handles shared configurations in project-level migrations, refer to the official documentationSingle-project snapshots.