Actions
Bug #4092
closedInvalid option 'None' in multichoice dropdowns in Event search
Start date:
05/15/2018
Due date:
% Done:
100%
Estimated time:
To be discussed:
Description
Several multichoice dropdowns on Event search contain the option 'None' which, when selected, results the Search to fail with "'None' is not a valid choice for this field".
How to reproduce:- Set up query with Severities set to 'None', press 'Search'
- A warning "'None' is not a valid choice for this field" appears below the Severities multichoice element.
- Behavior confirmed for other multichoices offering 'None' option (Source types, Categories, Classes, ...)
- Option 'None' appears for columns containing NULL values at data level. Correct behaviour therefore probably is:
... WHERE "cesnet_eventseverity" is NULL ...
or (in case of multi selection):... WHERE "cesnet_eventseverity" is NULL OR "cesnet_eventseverity" = ANY(ARRAY[#1, #2, ...]) ...
Related issues
Updated by Jan Mach over 6 years ago
- Status changed from New to Resolved
- Assignee changed from Jan Mach to Radko Krkoš
Attached commit resolves the issue, it can be closed.
Updated by Jan Mach over 6 years ago
- Related to Bug #4091: Option "<< no preference >>" for multichoice selectors in Event search translates to probably unintended query added
Updated by Radko Krkoš over 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
Revision 85fc0c01 removed the 'None' option. Filtering for untagged events is facilitated by the "<< without value >>" option. Fixed.
Updated by Jan Mach over 6 years ago
- Target version set to 2.0
- Parent task deleted (
#3734)
Actions