Actions
Defect #31487
closed
Issues filtering
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues filter
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Invalid
Affected version:
Description
For filters that support ANY clause there is a "is not null" check.
E.g. I want to filter issues by Assignee = any, in practice we will see that issues are filtered by field assigned_to_id = any BUT not null. However there're issues that assigned to no one and query result feels kinda strange.
Is it intended feature of defect?
Attaching patch to remove "not null" check in any clause.
Files
Updated by Go MAEDA over 5 years ago
- Category set to Issues filter
- Status changed from New to Closed
- Resolution set to Invalid
I think the behavior you pointed out is the expected behavior. I often use "any" operator to filter issues with any assignee is set, or issues with any target version is set.
You don't have to use the assignee filter if you want to get an issues list which does not take the assignee field into account. Just simply disable the assignee filter.
Actions