Problem Definition

The current behaviour is JRASERVER-9367 - when the JQL search does not fit into the custom field scope, the UI will show the custom field on the Issue Navigator with '!' and the user will not be able to choose the field.

This creates a big usability issue for end users in a complex JIRA environment where customfields are configured with very specific project/issue-type contexts, because end users are often not going to know or remember what specific project or issue type combination is applicable to the custom field they are trying to use in the issue navigator.

Suggested Solution

Allow the user to choose the custom field and then return the result based on the custom field scope.
or
show the custom field's context when the user hovers over the on the custom field at Issue Navigator.