Data Loss Prevention

This page describes situations where a snapshot's deployment may cause data loss, i.e. deleting data from issues, and how CMJ handles these cases.

1 Deletion of project versions and components
2 Ambiguous custom field matching
3 Deletion of custom field context with options

Deletion of project versions and components

Deleting versions/components will permanently remove their reference from issues on the system. An error message is shown if a migration case is detected (i.e. there are issues referring to the deleted objects) and the deployment is stopped. The error can be reduced to warning and the deployment will be allowed - this is controlled from General Settings' "Stop deployment in case of possible data loss" option.

Ambiguous custom field matching

In case there are duplicate custom fields in either the snapshot or the target Jira an error will be shown and the deployment will be stopped. The error can be reduced to warning and the deployment will be allowed - this is controlled from General Settings' "Stop deployment in case of possible data loss" option.

Deletion of custom field context with options

When a custom field context containing options is going to be deleted we show an error message and the deployment will be stopped. By default, an error message will be shown and the deployment will be stopped. This default behavior can be reduced to warning and the deployment will be allowed - this is controlled from General Settings' "Stop deployment in case of possible data loss" option.