-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Critical
-
None
-
Affects Version/s: 1.8.15, 2.0.3
-
Component/s: Frontend (F)
-
Environment:Zabbix 1.8.13
Just look at attached image.
I don't know how to explain it in english, but I'll try
When some of conditions are "not" they have to use AND instead of OR to communicate with same type conditions.
I've found this bug on Zabbix 1.8.13. I checked it on Zabbix 2.0.3 too - same result.
- duplicates
-
ZBXNEXT-1133 Improve flexibility for action conditions
-
- Closed
-