Fields cannot be queried via Basic search

Summary

When a Next-gen project is created with the same issue type as the existing classic projects, some fields cannot be used in the Basic search

Steps to Reproduce

Scenario 1 :

If you have a Classic Project and a Next-gen project, after configuring the default configuration scheme for a Custom Field with context defined for any issue type present in the next-gen project, when performing a basic search filtering for that Custom Field, the following message is returned: "Field is not applicable to the current project and/or issue type".

We created a video reproducing this problem as you can see here: JRACLOUD-71320.mp4
This video shows that the search works before creating the next-gen project, but it doesn't after creating it.

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 scheme with any issue type present in the next-gen project.
6. Try searching for issues using that Custom Field and some type that exists in next-gen projects on Basic Search

Scenario 2 : System Fields

1. Create a classic Scrum project. Make sure that Story issue type is used by the project.
2. Create a Sprint and assign some issues.
3. Perform a basic search on the Classic Project, Story Issue type and Sprint. (Works OK)
4. Create a Next-Gen scrum project. Make sure Story issue type is used by the project.
5. Try to perform a basic search again on the Classic Project, Story Issue type and Sprint

Scenario 3 : Custom Fields

1. Create a classic project. Make sure that Story issue type is used by the project.
2. Create a Custom field and assign to the screens of the classic project
3. Perform a basic search on the Classic Project, Story Issue type and Custom_Field. (Works OK)
4. Create a Next-Gen scrum project. Make sure Story issue type is used by the project.
5. Try to perform a basic search again on the Classic Project, Story Issue type and Custom_Field

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".

Notes

This seems to happen because Jira is mistaken the global issue type with the next-gen issue type.

Workaround

• Using Global context on the Custom Field configuration makes the behavior not reproducible anymore.
• Use the Advanced search and JQL should still work.