-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Medium
-
None
-
6
-
Severity 3 - Minor
Summary
When working with the single line text field, you can easily perform a search agains the issue. However the issue will populate in JQL searches for whatever data the field contained prior to being re-set to EMPTY.
JQL will still filter the issue by the "IS EMPTY" JQL search criterion, however it does show up in a search if it matched previously.
Environment
Cloud
Steps to Reproduce
- Create a single-line text custom field.
- ensure that you can easily modify the field on some issues
- on a new issue, populate the new field
- Search using TEXT LIKE operator (~) for what you populated in that field, the issue should show up
- Remove the content in the field from the issue
- Search again
Expected Results
The search will no longer populate with the issue.
Actual Results
The issue will show up in the search results in spite of being Null/EMPTY
Notes
none
Workaround
Only workaround known is to filter out by adding "AND CUSTOM_FIELD NOT EMPTY" to your JQL search.
- duplicates
-
JRACLOUD-76116 JQL for Single-line Text Field finds issue by value even when that field was cleared
-
- Closed
-
- is duplicated by
-
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
-
- is cloned by
-
JCES-547 Loading...
- mentioned in
-
Page Loading...