Fields are not searchable if -1 issue type (legacy all issue types) appears in the custom field config

Issue Summary

Fields are not searchable if -1 issue type (legacy all issue types) appears in the custom field config

Steps to Reproduce

1. Create a custom field, update its default custom field context so that it is set to issuetype -1 (You will need to have access to tenant database to do that).
2. Create issue with the field value set.
3. Search for the issue with JQL by the field and the value.

Expected Results

Issue returned.

Actual Results

Issue isn't returned.

Workaround

Clean legacy entry in custom field context table, so that there are no entries that point to -1 issue type (legacy All Issue Types).