Question
When using the placeholder {{ticket.title}}
in a trigger or automation, the placeholder doesn't render the ticket subject and instead displays Untitled ticket. How do I stop that?
Answer
The placeholder {{ticket.title}}
displays as Untitled ticket when it's used in a notification sent to an end user from a ticket without public comments.
When a ticket has no public comments it is considered a private ticket and is invisible to end users. As private tickets aren't visible to end -users, Zendesk won't send information from these tickets in notifications to end users.
To prevent this from happening, ensure there is at least one public comment on the ticket, making it visible to end users. For more information, see this article: Adding comments to tickets.
8 comments
Steve Eli
This feels like a bug to me rather than working as designed. I understand the no public comments thing, but rather than just electing to not populate anything, Zendesk choose to populate "Untitled ticket".
1
Tobias Hällgren
Agree with Steve, this feels more like a bug. Is there any plans on fixing this?
We are currently using Babelforce integration for phone calls and SMS, and everytinh is internal notes. We still however wants to measure satisfaction of these tickets, but now we have the above mentioned problem that they are sent asking for feedback on untitled ticket.
I can't really find any good workaround in the links provided above in the article.
0
Noly Maron Unson
Hi Steve and Robert,
I understand where you're coming from so I've marked this as product feedback for review, which means that your input will be aggregated as a part of our Voice of the Customer program that provides customer feedback to our product development teams.
Thank you.
0
Rob Johnson
We are also having this issue. Please allow us to use the subject of a ticket in triggers even if all the comments are private.
1
Christine Diego
Thanks for explaining your use-case. I've marked this conversation as product feedback for review, which means that your input will be aggregated as a part of our Voice of the Customer program that provides customer feedback to our product development teams.
We truly value customer feedback and your voice and votes in the forums help influence future Zendesk functionality.
1
Ines Cerdan
+1 on that issue
0
Jim McNamara
I've run into the same “Untitled ticket” problem using {{ticket.title}} in both the Email Subject field and the Email body field of my notification triggers; the placeholder does not initially evaluate.
Note that the ticket's Subject ticket field and Events trace both evaluate correctly inside the ticket.
For all ticket updates however, the {{ticket.title}} placeholder does evaluate correctly using the same notification triggers.
Caveat: I'm seeing this condition only when receiving an Airtable form via Zapier.
If I generate a ticket via a simple email, {{ticket.title}} evaluates correctly all the time using the same notification triggers.
0
Paolo
This could be an issue with how the ticket was sent from Zapier going to Zendesk. In this case, more examples and information are needed. I would highly recommend reaching out to our Support Team for further checking. More information here.
Best,
Paolo | Technical Support Engineer | Zendesk
0