-
Type:
Bug
-
Status: Done (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: 5.4.43, 5.4.45, 5.4.47, 5.4.48, 5.4.49, 5.6.2.1-jira8, 5.6.7.1-jira8
-
Fix Version/s: 5.6.14
-
Component/s: Scripted Fields
-
Labels:
-
Sprint:SR4J Sprint 71
-
Critical Points:5.9
"Issue(s) picker" Script Fields do not support making comparisons and/or searching for null or EMPTY field values. For example, you are not able to make queries such as:
<Script-Field-Name> is not EMPTY <Script-Field-Name> != null <Script-Field-Name> in ("") <Script-Field-Name> in (null) etc...
Trying any of the above can result in a number of different errors; the most prevalent being:
The field '<Script-Field-Name>' does not support searching for EMPTY values.
Steps to Reproduce:
- Create a new "Issue(s) picker" Script Field with only a basic configuration (just a field name will do) and ensure you've attached it to some screens in a local project for testing.
- Navigate to the issue Search screen and make an advanced JQL query like:
<Script-Field-Name> != null
- Note the resulting error message:
The field '<Script-Field-Name>' does not support searching for EMPTY values.
- is related to
-
SRJIRA-3091 Issue Picker Field values do not render correctly in the Issue Navigator
-
- Done
-