Issue Summary

A select/Checkbox type field with multiple contexts shows None/Error on the transition screen for old/new experiences. 

Steps to Reproduce

1. Create a Select/Checkbox (option type) field with a few options as global context.
2. Create Jira tickets with existing options in a project
   
3. Add new context with the same options but associate it with the Project 
   
4. Add the Select/Option field on the workflow transition screen.
5. Change the status of the Jira ticket that has a transition screen present.
6. In Old Transition Experience:
   The existing value of the field becomes NONE; users end up with a field value changed. 
   
7. In a New transition experience, Field shows an error message to select the option(from the newly associated context)
   

Expected Results

In both Old and New transition experiences, existing field value should be retained despite having the same option name with multiple contexts.

Actual Results

Old transition experience: The field value is removed when the "NONE" option is replaced automatically on the transition screen.

New transition experience: The field shows an error message to select the options from the project scoped context.

Workaround

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

Advised to maintain single context.