Updating trigger deletes dependencies

[markyrules]

This may have been brought up before, if so I apologize.


Consider the following scenario:

1. Create 2 hosts based on a template which contains a trigger called "trigger {hostname}"

2. Create a dependency on the first host that points to the trigger on the second host.

3. Rename the trigger in the template to read "renamed trigger {hostname}"

All dependencies will be gone, which is a pain if you have a large number of hosts inheriting from that template.

Does anyone know if this is easily fixable?

-Mark

[richlv]

that sounds like a bug to me - report it on the tracker

[markyrules]

Thanks, done.

[xs-]

This bug is in since at least 1.4
Import/export do not keep dependencies as well.

[markyrules]

I believe I understand why this happens... I'm guessing that when you do any kind of update on a trigger on a template, (just clicking the save button will suffice), it updates the triggers on any host which inherits from that template. By update, I mean overwrite those particular triggers, including any custom dependencies you might have on them. I managed to work around this issue by taking any of those triggers that I might want to customize (i.e. add a dependency to a trigger on another host), copy them over to the same host, and then disabling the original trigger inherited from the template.

However, IMHO when one updates a trigger on a template, only the changes made to that trigger should be pushed to hosts. I'm not a coder by profession but I may try taking a look to see how difficult this might be.

-Mark

[richlv]

However, IMHO when one updates a trigger on a template, only the changes made to that trigger should be pushed to hosts.

i believe it should work like that for all entities - including items as well, and all of their paraneters, including enabled/disabled state.
while some of this area (regarding items) most likely will be cleared up in near future, unfortunately i didn't think about trigger dependencies having the same problem