-
Bug
-
Resolution: Fixed
-
High
-
31
-
Severity 3 - Minor
-
14
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Issue Summary
You can restrict the scope of custom field so they aren't available in all issues. You can do that per issue type, for example:
But, currently, the Basic search cannot perform searches using the restricted field as criteria even though the search matches with the scope that field is restricted to:
In that case, although I had selected the correct issue type the field was restricted to, I couldn't get its options. I was able to perform an advanced search and select the value, but when switching back, the value was not supported.
Steps to Reproduce
- Restrict the scope of a custom field to a specific issue type;
- Try to perform a basic search, using it as criteria along with the correct issue type.
Expected Results
You should be able to to select that field's options.
Actual Results
You cannot perform a basic search using the restricted field even though the criteria matches with its scope.
Workaround
Use advanced search instead.
- is related to
-
JRASERVER-40738 Basic Search: Allow searches that now show (Custom field) "is not applicable for the current project and/or issue type"
- Gathering Interest
- relates to
-
JRACLOUD-80784 Unable to filter issues via custom field having predefined values for specific Team Managed project using Basic Search
- Closed