Can't add template, thinks template is a host

[xxiii]

Trying to add a dependency from a trigger in a template to another trigger in the same template, and getting "Cannot add dependency from a host to a template."

The template already has several other triggers with dependencies on other triggers in the same template, so this used to work.

getting this error in 5.2, and in 4.2.

edit: sorry, I botched the subject, and apparently I can't change it. Meant to title "Can't add trigger dependency, thinks template is a host"

[xxiii]

I see this, which claims its fixed, in several 4.x, I'm running 5.2 (plus I was running into this issue in 4.2.6, and was part of my motivation for upgrading to 5.2, but problem still exists.)
[ZBX-16122] Error when trying to add trigger dependency - ZABBIX SUPPORT

And this still open and very old bug, with the last comment from someone requesting they fix it version 5:

[ZBX-8013] Adding trigger dependency between templates fails when template is directly linked with hosts - ZABBIX SUPPORT
not sure this one is exactly the same issue, but it certainly seems related.

I tried creating an entirely new trigger with the dependency already specified before hitting "add" and ran into the same error.

If I had to guess, the update process is going through existing hosts, and trying to link them to the template, instead of to that own host's copy of the depended-on trigger. I seem to recall that I got around this in the past by changing the dependency from "template name: trigger name" to just "trigger name", but I don't see a way to do that in the current UI. (or there was some sort of "add template trigger" button/link in addition to a regular "add" button, memory is fuzzy on that) In any case, I got the existing dependencies in there somehow, and now its apparently not possible (or you can't do it if there are any existing hosts linked to the template).

The existing dependencies are all in the form "template name: trigger name". when I go to a specific host, it looks like:
template name: trigger name Depends on: host name: trigger name (but the updater is trying to do template name: trigger name instead of host name: trigger name (taking a guess))

[xxiii]

I'm thinking the issue in ZBX-16122 still exists if the "other" template is actually the same template.