Issue Summary

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

Even across NextGen projects if the custom field name is not an exact match this will be disregarded since basic search fields are grouped with non-case sensitive options and then validation is called with case sensitive option.

Steps to Reproduce

Scenario 1 : 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 2 : 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

The system and custom fields should be usable on the Basic Search.

Actual Results

The system field or custom field cannot be used on the Basic Search and it fails with the error. "Field is not applicable for the current project and/or issue type".

Other system fields affected.

• Fix Version
• Component

Workaround

1. Use the Advanced search and JQL should still work.
2. Custom fields on Nextgen should exactly match other custom fields name, if a single char is different (case sensitive) this will be disregarded.