Hi all,

tl;dr: Is it a bug if "* -alert_status:RESOLVE OR -alert_status:DISMISS"
not works on Alert UI?

I'm experimenting with filtering from the alert UI. What I found is I can
run the following query directly against the REST API without any problem:
"* -alert_status:RESOLVE OR -alert_status:DISMISS"
But if I try to add the same filter on the Alert UI only the
alert_status:DISMISS applies to the query.
The reason is we identifying filters by filter.field so two filters to the
same filed (alert_status in this case) override each other.

Is this a bug? If it is, I'm happy to fix it.

Regards,
Tibor

Reply via email to