Zabbix 1.8.13

Of course, it's all about case when "Type of calculation" is automatic, i.e. "AND/OR"

when fixing, it should be checked what the server does in this case

It works according to documentation.

http://www.zabbix.com/documentation/2.0/manual/config/notifications/action/conditions?s[]=action&s[]=conditions#configuration

Related issue: ZBXNEXT-1133

I'm closing it as duplicate.

Hmm, ZBXNEXT-1133 was redeveloped as feqture request as I can understand.
But this problem is not feature request.
I suppose it's a bug. Calculation is wrong. Right? No? Don't you think so?
So where is new feature?
Where is common sense?

Here is second similar problem at zabbix-bug2.png.
"Host" and "Host group" condition types must communicate between them as same type.

After some thinking and seeing php code:
When "Type of calculation" set to "AND/OR" i.e auto, at calculation step on action web page it should:
1. If condition set to "NOT" ("<>" or "not like") it should be factored out as different condition type.
2. "Host" and "Host group" condition types must be considered as same condition type. For example, that types could be included in one round bracket.

I've swaped this rules because I saw such order in php code (actionconf.php, lines number 580-583).

P.S. I'm sorry for such bad and impolite English, I just don't know how to explain some quite difficult and technical things in English.

Ok, I think it's enough difficult and needs much new code in server and frontend.
I'm closing it. Big sorry for that noise.

Just some small stupid ideas:
to solve problem №1: if condition operator is "<>" or "not like" you could introduce new condition type which can't be united under brackets with any condition types (including itself).
To solve problem with host and hostgroup condition types maybe you could make some exception in calculation logic to unite it under one bracket.

ZBXNEXT-1133 would probably be the proper solution and offer the most flexibility