---
title: "General settings"
canonical: "https://support.appfire.com/space/CMJ/198214114/General%20settings"
format: markdown
---
> Macro (aura-html)

## Configure general settings

The *General Settings* page provides options for configuring the snapshot deployment and creation process. There are various settings for you to choose from, such as configuring deployments, logging levels, adjusting analytics data, etc.

![image](media://c361bf7a-f940-4337-9215-ccc7a992aac8)

### Deployment settings

- **Stop deployment in case of possible data loss - **if checked, CMJ will show an error message and stop deployment if there is a possibility of data loss, e.g. ambiguous object matching, deletion of versions/components used in issues, etc. A warning message is shown otherwise. For more information check [Data Loss Prevention](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/197923030).
- **Use native Jira transactions** - if checked, Configuration Manager will perform the deployment in a native Jira transaction. Otherwise, no transaction will be used.  
:warning: If this option is disabled, perform a DB backup of the system before deploying a snapshot.

> ⚠️ As of CMJ 6.14.0 the “**Do not merge Versions and Components” **option has been removed due to an update to the deployment skip options.   
> ⚠️ [Learn more](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198021794) about the new skip options available during a snapshot depolyment.

- **Persist deployed snapshot to current system native ID mappings **-** **if checked, CMJ will persist the mapping of the configuration objects' native IDs from the snapshot to the matched objects' IDs from the current system after a deployment in a JSON file. The file's location will be logged in CMJ's Audit log. The mapping will include all [root objects and versions/components](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198246502).
- **Keep skip merge selections** - if checked, CMJ will apply your last selections in the skip object merge options to all subsequent deployments.
- **Issue data import errors threshold** - if checked, CMJ will limit the number of errors in issue data per project that are allowed before the import operation for this project is aborted.
- **Do not lock the Lexorank table when ranking issues during deployment** - if checked, Configuration Manager will not lock any rows in the Lexorank table during the issue ranking phase** **of snapshot deployments. Issues can still be ranked manually during the whole** **deployment process. This option is recommended for small deployments on large live instances.

### Logging settings

- **Enable DEBUG level logging for CMJ **- If checked, CMJ logging will be set to level DEBUG and all CMJ-related logs will be appended in JIRA_HOME/log/botronsoft-cmj.log.  
:warning: Enabling this option may degrade CMJ's performance.

### Analytics settings

- **Allow collecting analytics data - **enable or disable gathering analytics data for some Configuration Manager events.