Hello,
One of biggest problems when working with Zabbix is missing (weak) dependencies between different components. This is due to completeness and featurefulness of Zabbix, as there is a cost for each added complexity.
One of highly probable human errors happen when someone adds a "Trigger name contains" condition to an action (Like "exception in"), but later rename that part of trigger name (e.g. to "exception at") and forgets to update depending action as well.
There can be a function which is called before renaming a trigger and searches for such actions, showing a warning dialogue if such action found. Of course, it can't be a silver bullet, especially where a low level discovery macro is involved, but it's quite useful at preventing human errors. More such cases are imaginable wherever a contains/equals condition exists (e.g. renaming a tag while there is a event correlation depending on it).