On this page:
| Table of Contents |
|---|
Custom field context deletion
We aim to manage custom field contexts and their options as sophisticated as possible during the:
...
To give you the tools to avoid such situations, first, we need to go through how we evaluate the source and destination contexts to find out if they match.
How do we evaluate and match source and destination contexts?
You should first know that for each custom field, CMJ Cloud exports the contexts only of the projects in the deployment/migration scope. These are either the global contexts or contexts for the projects in the migration/deployment scope.
...
The problem comes when you have a destination context and all its projects are present in a source context. Then, CMJ Cloud will attempt to execute its logic from above to remove the source projects from the destination context. As a result, this will leave the destination context without any projects, and it should automatically become a global context. CMJ Cloud can’t let that happen on the destination, as a project can have only a single global context. That’s why it stops the deployment on the Analyze changes phase and shows you the error about the potential consequences of deletion.
How to resolve the context deletion error?
If the context deletion works for you, we recommend removing the context from the custom fields it’s assigned to on the destination Jira Cloud by yourself.
...