Summary

In versions which have JRASERVER-62455 : Changing a custom field configuration changes the values of custom fields when issues are edited fixed, changing a custom field's contexts and options will no longer cause the deletion of newly-invalid values in issues.

Instead, these invalid values will remain, with a "(not available)" suffix attached to the value to indicate to the users that the value is no longer valid in the current configuration. This allows users to identify these issues and retain the value as they update it to a new value that is valid.

It would be helpful to implement a way for administrators to be able to check all of the issues in the instance that may contain invalid field values, on a field-by-field basis.

Suggestions

Implement a feature in the Custom Fields administration page which, for all custom fields, checks for all issues in the instance which contain invalid values for that field.