---
title: "Skip individual changes"
canonical: "https://support.appfire.com/space/CMJ/2506653713/Skip%20individual%20changes"
format: markdown
---
> Macro (aura-html)

## Overview

Skipping changes gives you precise control over which configuration changes are applied during a deployment. It lets you deploy only what you need, making deployments more flexible and reducing unnecessary changes.

There are two types of changes: major and minor. Major changes are the main configuration elements (such as projects, workflows, and custom fields). Minor changes are the components of those elements (for example, descriptions, options, contexts, etc.).

---

## How it works

1. **Start a snapshot deployment**
2. **Analyze phase**
  - Let CMJ run the deployment analysis.
  - CMJ presents a list of changes.
  - Each modification ([M]) and deletion ([D]) has a checkbox.
3. **Skip a change**
  - To skip a major configuration object, uncheck the box next to it. This skips the object and all associated minor changes shown on the right.
  - Example: *Uncheck the project "homosapien” as shown in the screenshot below. This also skips its description modification, as indicated on the right.*
  - Alternatively, you can use the top checkbox to check or uncheck all the elements in your current tab.
4. **Reanalyze the deployment**
  - After unchecking a configuration object, a warning prompts you to reanalyze the deployment.  
:info: Keep in mind that [Bulk selective merge](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198117040) doesn’t support skipping minor changes, and these changes won’t appear in your exported file.
  - Click **Analyze** to re-evaluate the changes based on your selections.
  - Example: *Skipping all modifications to the project “homosapien”, as indicated by the screenshot.*
  - CMJ recalculates the deployment and excludes all skipped changes.
5. **Deploy the snapshot**
  - Click **Deploy** to start deployment.
  - Audit log entries are created for skipped items.
6. **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 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.

**IMPORTANT!** You cannot skip any changes to:

- *automation rules *
- *issue type schemes*
- *priority schemes*
- *workflows*
- *workflow schemes*
- *field configurations*
- *position*, *order*, or *sequence* attributes of configuration objects
- additions or deletions of reference changes affecting *dashboards* (e.g, column layout changes for dashboard gadgets cannot be skipped)
- *JSM projects *if the changes include
  - *Service Desk Email Channel*
  - *Request Type Groups*
  - *Request Types*
  - *Service Management Automation Rules (a.k.a. Legacy Automation)*
  - *Confluence KB links*

Furthermore, the skip functionality is not available when using the **System Restore** mode.

> 📝 **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](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198214114) page.

---

## Audit logs

Configuration Manager adds an audit log entry for all manual skips you made during the deployment.

![image (4).png](media://c5e2669e-a176-486c-8b12-9222e8e70eb9)

---