A template's new triggers being created in a different template

[sibr]

For one template, if I create a new trigger it ends up on another, similarly named but different template. In the screen shot, the other template already has a trigger of the same name, and so it doesn't let me add it. If I create a trigger with a unique name, then it the trigger gets created in the wrong template. These two templates are not linked to each other.

Other objects I've tried seem to work fine (graphs, items, macros). Also, I can create triggers from a third template and they get created in the correct template. So it doesn't seem like user error on my part.

Possibly related: only just upgraded from 6.0 to 6.2.3 today.

[sibr]

Trying to work around this, but using a Clone or Full Clone of any template also is failing -- just returns me to the list of templates with a message of "Template updated". I guess try exporting and importing?

Alternately, if someone could point to me where there template data is stored. Sure seems like this is a case of a tweaked template ID somewhere.

[MattK]

I had this issue when I was copying a trigger condition from one template to another:

nodata(/CM 1.5.0.x/agent.ping,5m)=1

The CM 1.5.0.x must be set to the current template otherwise it'll attempt to add it to the one you copied it from.