-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: Work Item - Search - Backend - JVIS
-
14
-
Severity 3 - Minor
-
12
Issue Summary
Once you set a value for a Text Field single-line (custom field) and then clear that value, Jira's JQL will not recognize that field as EMPTY anymore.
Steps to Reproduce
- Create an issue with a custom field (single-line text field)
- remove the custom field value later
- Make a JQL search:
"singleLineTextFielsName" ~ "fieldvalue"
Expected Results
The field should be considered as empty again since no information is set.
Actual Results
JQL still shows the issue where the field is no more set.
Rest API shows correct data.
Workaround
As a workaround, you can exclude these issues by adding AND custom_field IS NOT EMPTY to your JQL search.
You can also allow Automation for Jira to properly clear this field for you by running an automation that updates this field to a "NULL" value. You can import this rule and apply it to your own text field: automation-rule-2616645-202111011333.json
Note: This can also happen with Read only custom fields where similar behaviour can be seen.
- is duplicated by
-
JRACLOUD-69792 Single-line text custom fields will show in search if value is set to Null
-
- Closed
-
-
JRACLOUD-78084 Deleting the value from a text custom field will return issue when searching that field's original value in JQL (value is not entirely deleted on back end)
-
- Closed
-
- was cloned as
-
JRACLOUD-80981 JQL for read-only text fields finds issue by value even when that field was cleared
-
- Closed
-
- depends on
-
JQLVS-21 Loading...