Issue Summary

When a Next-gen project is created with the same issue type ( eg Epic, Task, etc ) as the existing classic projects, we are unable to query the custom field value in the Basic search

Steps to Reproduce

1. Create a Classic project
2. Create a Next-gen project
3. Go to Administration > Issues > Custom fields
4. Navigate to that Custom field, then go to Cog Icon > Configure

5. Edit the Applicable contexts for the scheme with any issue type present in the next-gen project. ( So if you refer above-attached screenshot, I have added Task in the field scope, Task is used by both Classic and Next-gen project)

6. Try searching for issues using that Custom Field on Basic Search

Expected Results

You are able to select the Field on the Basic Search.

Actual Results

A warning is shown on the UI: "Field is not applicable for the current project and/or issue type" and so not able to list the options for the custom field. Please refer to the 2nd screenshot attached.

Workaround

Use the Advanced search and JQL should still work. ( referring to the first screenshot)