Tickets Not a Bug {name} is not parsing

[Alpha1]

The variable {name} is not parsing in tickets. I have not tried other variables but I assume the same issue is at play.

 

[Naz]

In escalations or predefined responses?

 

[Alpha1]

In predefined responses.

 

[Freelancer]

It is running well with my latest install. @ALfa1 are you sure you have rebuilt all caches and indexes?

 

[Alpha1]

There are only 3 rebuilds to run, which I have. What else can I do?

 

[Freelancer]

Have you tried to edit and save the responses again? Does the {name} not work too if you create a response? I edited all my (three harr harr) responses after update and it works.

 

[Alpha1]

Actually {staff} doesn't parse. {name} does parse.
Even after saving my responses.

 

[Freelancer]

There is no {staff}.... only {staffName}

 

[Alpha1]

I have been using {staff} for quite some time. @NixFifty has this changed?

Anyhow, that fixes the issue. Thanks.

 

[Freelancer]

It seems to have changed and all placeholders are working. I tested it today.

{staffName} seems to be the "Board Admin"? Can we edit that or if not, could we just name the placeholder "{admin} then?

 

[Naz]

I have been using {staff} for quite some time. @NixFifty has this changed?

Anyhow, that fixes the issue. Thanks.

Yeah, {staff} became {staffName} in 1.5.2 to clear up some confusion as to what it did. Forgot to note that in the release notes though, my mistake.

{staffName} seems to be the "Board Admin"? Can we edit that or if not, could we just name the placeholder "{admin} then?

{staffName} would be whoever is replying. In the case of escalations or predefined responses, it's usually a staff member. Unless you're referring to something else, of course.

 

[Freelancer]

{staffName} would be whoever is replying.

Even better.... that I like