Hi! Let’s fix why your Zendesk ticket prints missing timestamp (for example created at, updated at, first reply time, or comment time) when you click Print ticket or generate a PDF.
Quick details so we target the right “print path” (Zendesk has a few):
• Are you printing via Ticket options → Print ticket (the built-in printer-friendly view), or via an app/integration that exports to PDF?
• Which timestamp is missing: ticket.created_at, ticket.updated_at, solved time, or comment timestamps?
• Is the timestamp visible on-screen in the ticket UI, but disappears only on print? Or is it missing everywhere?
• Do you rely on custom fields and a field map (mapping ticket fields into a template), or is it the default print view?
• Any special requirements: a specific date/time format (MM/DD vs DD/MM), timezone conversion, or “include time + seconds”?
Once I know which method you use (printer-friendly view vs template/PDF tool), I’ll walk you through the exact fix: either ensuring the field has a value so Zendesk prints it, or correcting the field mapping / placeholders so the timestamp renders in the output.
Customer
We’re using Zendesk Support. Agents open a ticket, click the three dots menu, and choose Print ticket. The printed page is mostly fine (subject, requester, description, custom fields), but the timestamp is missing. We specifically need “Created” and “Last updated” to show on the printed ticket for compliance. On screen we can see activity and time, but on print it’s not there. We also have a custom form with multiple ticket fields and some are reordered in Admin Center.
Got it — you’re using the built-in printer-friendly view (“Print ticket”). Here’s the key behavior that causes this exact issue:
✅ Zendesk’s printer-friendly view prints ticket fields that have values and that are part of the printable layout.
❗ The timestamps you care about (Created, Updated) are system properties of a ticket (think: created_at / updated_at), not always displayed as standard “ticket fields” in the print layout by default.
So when people say “Zendesk ticket prints missing timestamp,” it’s often one of these scenarios:
• The print view simply doesn’t include created/updated metadata in your account’s printable section.
• You’re expecting a timestamp stored in a custom date/time field, but that field is actually blank (Zendesk won’t print empty fields).
• The “timestamp” is coming from comments (comment created time), which the basic print view may not show how you expect.
We’ll solve this cleanly with a “field map” approach: add a printable timestamp via placeholders (and optional Liquid markup for formatting), so the output always includes the date/time in a consistent format — even if the default print view hides it.
Customer
That makes sense. We do have a custom date field too, but it’s not the one we need. We need the actual ticket created/updated time. Where do we add placeholders for printing? We don’t want to break the agent workflow — they just need the Print option to include the timestamp.
You’re right to be cautious — the native Print ticket page isn’t designed like an email template where you can freely inject placeholders in a WYSIWYG editor. So the practical “field map” solutions teams use are usually one of these (all keep the workflow simple):
Option A — Store timestamps into a printable custom field (field map workaround)
You create/choose a custom ticket field (date/time or text) that will print, then automatically populate it using a business rule (trigger/automation) with the ticket timestamps (created/updated). That field becomes your reliable “printed timestamp.”
Option B — Use a print/PDF app that supports a template + field mapping
Many teams use a PDF/print workflow where you have a template and a field map (ticket fields → placeholders), so you can place {{ticket.created_at}} and {{ticket.updated_at}} exactly where you want, format them, and include comment timestamps if needed.
Before we choose A or B, let’s confirm what you’re allowed to change: do you have admin access to create a new custom field and a trigger, or do you prefer a “no admin changes” approach using a template tool?
Customer
We have admin access in Zendesk. We can add a custom field and a trigger. We’d prefer to keep using the built-in Print ticket page if possible. But if the only reliable way is to map timestamps into a printable field, we can do that. We also need the printed time to be in our local timezone, not UTC, and ideally include both date and time.
Perfect — then Option A is the fastest “field map” fix for the native print view: we create one or two printable custom fields and keep them always populated, so the printer-friendly view can’t “forget” them.
Step 1 — Create two printable fields
In Admin Center → Objects and rules → Tickets → Fields, create:
• Printed Timestamp — Created (text field is the most flexible for formatting)
• Printed Timestamp — Updated (text field)
Why text? Date fields can format differently or omit time; a text field lets us store “YYYY-MM-DD HH:mm (TZ)” or any compliance format you need.
Step 2 — Populate them using placeholders (field map)
Create a trigger that runs on ticket creation (and optionally on updates) that sets those fields using placeholders like:
• {{ticket.created_at}}
• {{ticket.updated_at}}
If you want a nicer presentation (timezone + formatting), we can use Liquid markup formatting where supported. If your specific action editor doesn’t allow Liquid formatting directly, we’ll still store the timestamp consistently, then handle timezone/format expectations by standardizing the string format your team accepts (for example including the timezone label).
Step 3 — Ensure fields appear on the ticket form
Add those two fields to the form used by your agents (even if read-only in practice). The printer-friendly view prints fields that have values — so once these have values, they should show up when agents click Print ticket.
Customer
I created the two fields and added them to the form. I also made a trigger that sets them using {{ticket.created_at}} and {{ticket.updated_at}}. After testing, the created one filled in, but the updated one is inconsistent — sometimes it’s blank, sometimes it shows an old value. And when we print, one of the fields still doesn’t show up on the print view.
That’s a very common “field map” gotcha, and the symptoms match two specific issues:
Issue A: The trigger timing for updated_at
If your trigger runs on “ticket created” only, then {{ticket.updated_at}} can be the same as created time at first — and later it changes, but your “Printed Timestamp — Updated” field won’t automatically refresh unless you also update it on subsequent ticket updates.
Fix: Create a second trigger that runs on ticket updates (or specific update events) and always refreshes your “Updated” print field using {{ticket.updated_at}}. Make sure it’s not restricted by conditions that skip common updates (like internal notes, status changes, or field edits).
Issue B: Zendesk print view hides fields with no value
The printer-friendly ticket page prints only fields that currently have values. If “Updated” is blank at print time, it won’t appear at all — which looks like “Zendesk ticket prints missing timestamp.”
Fix: Ensure your “Updated” field is always populated after the first update. For compliance, some teams set the updated field to created time initially, then overwrite it on the first true update. That guarantees it prints even for brand-new tickets.
Customer
We added a second trigger to update the “Updated” print field when a ticket is updated, and now both fields usually have values. But the printed timestamp looks like a long string and the timezone is confusing. Also, our team asked if we can print the timestamp of the last public reply, not just ticket.updated_at, because internal notes change updated_at too.
Great refinement — and it’s exactly why the “field map” approach is powerful: you can decide which timestamp you actually mean by “timestamp.” Let’s handle both concerns: formatting/timezone, and “last public reply time.”
Step 4 — Use clear labels + consistent format in your printable fields
For compliance prints, don’t rely on ambiguous labels like “Updated.” Use explicit text in the field value, like:
• Created: {{ticket.created_at}}
• Last change: {{ticket.updated_at}}
Even if the raw placeholder output includes timezone/format you don’t love, the printed ticket becomes understandable because it’s labeled and consistent across all tickets.
Step 5 — Track “last public reply timestamp” separately
You’re right: ticket.updated_at changes on internal notes and field edits. If you want “last public reply,” create another custom field like:
• Printed Timestamp — Last Public Reply
Then set it only when a public comment is added. The trigger conditions should target “comment is public” (not internal note), then store a timestamp into that field. This becomes your accurate “customer-visible activity time” on printouts — a frequent related search term is “Zendesk ticket print last public comment timestamp.”
If you want, we can also align the formatting further using Liquid markup where your rule editor supports it; otherwise we keep it stable and readable with consistent labels and local process standards.
Customer
That worked. We now have Created and Last Public Reply stored in fields and they show up in Print ticket. One more problem: on some tickets, the fields appear in a weird order in the printer-friendly view, and a few other custom fields don’t print at all. Is that related to our field mapping?
Yes — and the fix is straightforward. Two Zendesk rules apply here and they both affect “field map” outcomes on printing:
Rule 1: Printer-friendly view only prints fields with values
If a custom field is empty, Zendesk won’t print it. That’s why some fields “don’t print at all” — it’s not broken mapping; it’s “no value at print time.”
Rule 2: Print view follows ticket field order from Admin Center
If you re-ordered fields in Admin Center (or you have multiple forms), the printer-friendly view can reflect that order. If the “timestamp fields” need to be near the top for compliance, move them higher in the form’s field order (or ensure they’re included in the specific form used by those tickets).
Quick checklist (prevents future ‘Zendesk print missing timestamp’ tickets)
• Confirm your printable timestamp fields are on every relevant form (multi-form accounts often miss one).
• Ensure the triggers populate them for the right ticket types and brands.
• For any field that “must print,” ensure it’s never empty (set a default value like “N/A” if compliance requires the label to appear).
With this, your print layout becomes predictable: fields print, in the order you expect, with the exact timestamps you mapped.
Customer
Awesome. We moved the timestamp fields higher in the form and set default text if empty. Now Print ticket consistently includes Created and Last Public Reply, and the order looks correct. If later we switch to a PDF app, will these same placeholders and field IDs still apply?
Yes — and that’s another benefit of what you did. When you later use a print/PDF tool with a template + field mapping, you’ll have two stable options:
Option 1: Map directly from system timestamps
Use placeholders like {{ticket.created_at}} and {{ticket.updated_at}} inside the template (often with Liquid markup to format date/time). This is the “cleanest” if the tool supports it.
Option 2: Map from your printable timestamp fields
Since you already created “Printed Timestamp — Created” and “Printed Timestamp — Last Public Reply,” you can map those custom fields by their field IDs (for example {{ticket.ticket_field_<ID>}}). That’s extremely reliable because the value is already pre-processed by your triggers and guaranteed to print.
Either way, your “timestamp field map” becomes reusable across printing methods — printer-friendly view today, PDF templates tomorrow — without changing agent workflow.
Customer
Great. We’ve got it working now and the compliance team is happy. Thanks for the step-by-step and for explaining why Zendesk hides empty fields on print — that was the missing piece for us.
You’re welcome! Quick recap of the accepted fix for
Zendesk ticket prints missing timestamp: the printer-friendly ticket view prints fields only when they have values, and it doesn’t always show system timestamps the way you expect. The most reliable approach is a
field map: create printable custom fields (Created / Updated / Last Public Reply), populate them with
ticket placeholders via triggers, then place them high in the ticket field order so they appear on printouts consistently.
Want me to review your trigger conditions (public vs internal comments), timezone expectations, and the exact placeholder set for your account?
Start a chat and an expert can dial it in fast.
How to confirm it’s a field-map issue vs an empty-value issue
If a timestamp field doesn’t print, first confirm whether the field has a value at print time. Zendesk won’t print empty ticket fields. Next, verify the ticket is using the correct form (multi-form environments are a frequent reason for “missing timestamp on printed ticket”). Finally, validate that your triggers refresh the “updated” timestamp on real updates and that your “last public reply” timestamp updates only on public comments.
If you later switch to a PDF tool, you can either map timestamps from system placeholders like {{ticket.created_at}} or map from your custom field IDs using {{ticket.ticket_field_<ID>}}. Both methods keep your printable timestamps consistent.
Zendesk ticket prints missing timestamp — quick troubleshooting tips
Stabilize printing with a timestamp field map: store what you need in printable fields.
Fast path: create 1–3 printable custom fields for Created / Updated / Last Public Reply, populate them via triggers using ticket placeholders, add them to every form, and move them near the top of the field order. If a field must appear even when unknown, set a default value (like “N/A”) because Zendesk print view hides empty fields.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your Zendesk setup, forms, and business rules, please consult a verified expert on Whizz-Tech before changing triggers or field configurations.