Consider the following scenario:

1. Create a template called "template_generic_host", and create an item "item_a", along with two triggers, "trigger_item_a_warning on

{HOSTNAME}", and "trigger_item_a_critical on {HOSTNAME}

". Create a dependency on "trigger_item_a_warning on

{HOSTNAME} which points to "trigger_item_a_critical {HOSTNAME}

.

2. Create a host called "host_a" and link it to "template_generic_host". Notice that the dependency on trigger "trigger_item_a_warning" will read "Depends on: trigger_item_a_critical template_generic_host" when it should read "Depends on trigger_item_a_critical host_a".

Workaround:

Open the trigger on "template_generic_host" and click "save". The dependency on host_a will be corrected.