Issue Summary

Currently, if a custom field has two contexts set, such as a Global Context and a Project-Based context, and the options used for a particular project are from the Project-Based context, if a user would like to switch to using the Global Context instead, we are unable to migrate the options in the issue from one context to another.

Steps to Reproduce

1. Create a Custom field for Eg : Select list single choice
2. Add a 2 options to it, for Eg : A & B and set the context limited to a single project
3. Set the value to the field in any issues in that Project
4. Now add a global context for the same custom field with the same options i.e. A & B
5.  If a user wants to delete the project-based context by migrating the field values to Global context they can't do that.

Expected Results

User should be able to move the issue field options from context to another as we have a global context set

Actual Results

When performing a bulk operation to change the value of a custom field in an issue from project context to global context, the dropdown does not display the value from the global context.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available