Skip individual changes
Overview
Skipping changes gives you precise control over which configuration changes are applied during a deployment. In other words, it lets you skip specific changes and deploy only the ones you need.
This makes deployments more flexible and reduces the number of unnecessary changes.
How it works
Start a snapshot deployment
Analyze phase
Let CMJ run the deployment analysis.
CMJ presents a list of changes.
Each modification (M) and deletion (D) has a checkbox.
Skip a change
Uncheck the box next to a configuration object you don’t want to be modified or deleted.
Example: Uncheck the project "homosapien” as shown in the screenshot below. This will skip its description modification as indicated on its right.
Reanalyze the deployment
After a configuration object is unchecked, you’ll get a warning that asks you to use the Analyze button to re-evaluate the change according to the rest of your deployment.
Example: Skipping all modifications to the project “TestProject”, as indicated by the screenshot.
CMJ recalculates the deployment, excluding skipped changes:
Deploy the snapshot
Click Deploy to start deployment.
Audit log entries are created for skipped items.
Review the deployment
Limitations
CMJ does not allow skipping changes that could compromise the target system’s integrity; therefore, you can only skip Modifications and Deletions. However, you cannot skip the deletions of projects.
Additionally, you cannot skip any changes to the Default issue type scheme, Default priority scheme, and Default field configuration. However, all the other default schemes are skippable as expected.
Furthermore, you cannot perform multiple selective merge operations on a single element during the same analysis operation. For example, you cannot rename, rematch, and then skip a configuration object without clicking the Analyze button to confirm the pending changes first.
Effect of skipping changes on issue data
In some cases, skipping a change can have an impact on the imported issue data.
For example, if we skip a project modification, which in turn can skip the addition of a Component, Version, or if we skip a custom field modification, which in turn can skip its Custom field options. If any of those are used in the deployed issues, warnings will be included in the deployment results page.
If necessary, the Issue data import errors threshold can be increased or removed accordingly in CMJ’s General settings page.
Audit logs
Configuration Manager adds an audit log entry for all manual skips you made during the deployment.