(Note: This may be a documentation issue, to describe the expected behavior...)

The problem: triggers and items on a host that were expected to be removed by an "unlink and clear" API or UI call remain on a host. Manual intervention is necessary to cleanup "orphaned" items.

Observed behavior:

0. Have a host with a template that creates items and triggers
1. An item+trigger pair in an "alarming"/PROBLEM state – trigger active (this is what is suspected to leave the trigger+item around...)
2. "Unlink and clear" (i.e. /hosts.php -> Templates) the template from a host (via API or UI)
3. Observe triggers and items left on the host that should have been removed b/c they were on the template.

Is this "a feature" such that PROBLEM state triggers dont get "missed" when an unlink/clear happens?