Issue Summary

When configuring a custom field, there are options for multiple contexts to allow for the custom field to behave differently in different projects or issue types. If you enable a second context, the default global context is now ignored. When using the "Where is my field" link, it shows:

The field 'CUSTOM FIELD' is not configured in scope of the project 'PROJECT' and issue type 'TYPE'
To solve this issue, go to 'CUSTOM FIELD' configuration page and add it to the scope

Steps to Reproduce

1. Create a custom field (tested with single select)
2. Open the field configuration
3. Add new contexts with different options for a specific issue type
4. Go to a screen that contains the field based on the default context

Expected Results

See the default context on the screen (with the new context showing in the corresponding screen)

Actual Results

The field is not included in the default context (new context shows as expected)

Workaround

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