google translate :
--------------------------------------------------------
The problem is that when a mass update trigger level (severity), whether on the level or pattern of the host in the presence of established relationships (dependency) to these triggers, resets these dependencies.

example:
1. Choose any triggers, for which we want to change the level (severity): Fig. "Scr1.Dependency.JPG"
We note that the selected triggers are set depending on!
2. Go into configuration mode triggers (Fig. "Scr2.TriggerSelect.JPG")
and select a new level (Fig. "Scr3.SetNewSeverity.JPG")
At the same time to change depending on triggers is not planned. Do not put the check for the item "Trigger dependencies".
3. After changing the trigger level, we obtain that the current dependence of triggers that were set for this moment, no!

--------------------------------------------------------
original :
--------------------------------------------------------
???????? ??????????? ? ???, ??? ??? ???????? ?????????? ?????? ????????? (severity), ?? ?????, ?? ?????? ??????? ??? ?????, ??? ??????? ????????????? ???????????? (dependency) ??? ???? ?????????, ?????????? ????? ???? ????????????.

??????:
1. ???????? ????? ????????, ??? ??????? ????? ???????? ??????? (severity): ???. "Scr1.Dependency.JPG"
????????, ??? ????????? ???????? ????? ????????????? ???????????!
2. ??????? ? ????? ???????????????? ????????? (???. "Scr2.TriggerSelect.JPG")
? ???????? ????? ??????? (???. "Scr3.SetNewSeverity.JPG")
??? ???? ?????? ??????????? ??? ????????? ?? ???????????. ?? ?????? ????? ??? ?????? "Trigger dependencies".
3. ????? ????????? ?????? ????????? ???????? ??? ??????? ??????????? ?????????, ??????? ???? ??????????? ??? ????? ???????, ???????????!