The scenario is where you have two templates with discovery rules assigned to a host.

The discovery rules discover triggers on the host and they are defined as discovered triggers allocated to the host.

A discovered trigger (T1) from discovery rule (D1) needs to have a dependency on the a discovered trigger (T2) from discovery rule (D2).

However through the front end or api add a dependency for the discovered trigger (T1).

What would be nice is just like you can enable/disable the discovered triggers directly on the host, that you can also add dependencies.

When updating the trigger prototype perhaps there would be an option 'keep/clear dependencies' which would not clear dependencies for existing discovered triggers.

In our case we have discovered an oid '.1.3.6.1.4.1.12356.101.4.8.2.1.3.XXX' (fgLinkMonitorState) and have a trigger when the link status is active/inactive, along with an oid '.1.3.6.1.2.1.10.7.2.1.19.XXX' (Duplex Status - Duplex Status) and have a trigger when the link duplex is half-duplex.

The condition is when the link is down the status defaults to half-duplex which will cause the duplex status trigger to fire, where as if we could put a dependency in place between the two discovered triggers it would not fire.

We use automation to put dependencies in place which is based on rules/queries so this would not be an issue for us.