When a parent template defines a dependency between two triggers in two separate child templates, the dependency is not included when the parent template is exported to XML.

I have read previous issues related to this problem and I'm confident that this use case has not been addressed.

For example, I have a template which is applied to all hosts. It has two child templates: Templates ICMP Ping and Template App Zabbix Agent. In the parent template, I define a dependency where {{Template App Zabbix Agent: Zabbix agent on

{HOST.NAME} is unreachable for 5 minutes}} depends on {{Template ICMP Ping: {HOST.NAME}

is unavailable by ICMP}}. This way, agent issues are muted if the host is unreachable.

When I export the parent template, this dependency is not exported with it. We wish to define many additional inter-template dependencies in this way, but cannot backup or source control the dependencies using XML exports.

I've reviewed the following issues, but these mostly apply to host exports, rather than composite templates:

• ZBX-5695
• ZBX-5453
• ZBX-2948
• ZBX-5299

Please add a feature that includes trigger dependencies between child templates when exporting or importing templates from XML. This way dependencies between templates may be managed effectively using source control and shared for convenience.