When administrators delete a custom field configuration context or move a project out of its current context into a different one, there is currently no native mechanism to re-map or migrate existing issue data to new values.

If the target context does not contain the exact same options, or if a context is deleted entirely, the underlying historical data on issues is permanently purged or orphaned. Administrators are forced to manually perform tedious steps to safeguard and update their data.

 
Expected Behavior:
When modifying or deleting a custom field context, Jira should evaluate whether there are active issues containing data for that context. If data exists, it should halt the immediate deletion/change and launch a mandatory, interactive Migration Wizard process.