This site is moving soon to become part of an integrated Appfire documentation and information site for our apps. This site will remain available during the transition to our new and improved site. Once this site is moved over, this banner will be updated with the new site link for easy access.

Take a look here! If you have any questions please email

General Settings

On this page:

Configure General Settings

The General Settings page provides options for configuring the snapshot deployment and creation process.

Deployment settings

  • Send ClearCacheEvent to clear Jira's internal caches after deployment - If checked, CMJ will send ClearCacheEvent after deployment. If unchecked, CMJ will refresh only the аffected internal caches. By default, it is unchecked.

  • For Jira Data Center it is highly recommended to leave this option unchecked.

  • 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. A warning message is shown otherwise. For more information check Data Loss Prevention.

  • Use native Jira transactions - if checked, Configuration Manager will perform the deployment in a native Jira transaction. Otherwise, no transaction will be used. If this option is disabled perform a DB backup of the system before deploying a snapshot.

  • Do not merge Versions and Components - skip the import of any changes to versions and components. The main use case for this is when doing project migrations - the project configuration is deployed on the target system using Configuration Manager and then the data is migrated using Jira's project import tool - however, the tool requires no changes to versions and components to be present in the target project.

  • 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.

  • 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 - Warning: Enabling this option may degrade CMJs performance. 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.

Analytics Settings

  • Allow collecting analytics data - enable or disable gathering analytics data for some Configuration Manager, Integrity Check and Power Admin events.