Jane Sullivan

We have just implemented our system and our business partners are getting our ticket numbers confused with their own ticket numbering system.  It would be great to have the ability to add a prefix to the ticket number so our tickets can be easily identified (as you can in NetSuite & Microsoft Dynamics).  This is causing quite big issues and mistakes for us and generating rework.

When I select the Due Date, if it is at a certain time of day, the date changes automatically to the next day according to the UTC date.  We are in NZ so this is happening frequently.  After the ticket is created, I can see the due date is set to the correct local date but the UI still reflects the UTC date.  This is causing issues with our staff who are trying to set the Due Date but can't see the date is set correctly until after the ticket is saved and having to check the Event history of the ticket.

Please can the Due Date reflect our local date and retain the correct value when it is selected?

Having a timestamp on a field is integral to our business.  We are currently using the below regular expression for date/time format of: DD-MM-YY HH:MM
\b(3[01]|[12][0-9]|0[1-9])-(1[0-2]|0[1-9])-[0-9]{2} ([01][0-9]|2[0-4]):[0-5][0-9]\b

This regex works but it will not validate the date nor can it be used for any automations, i.e. 31-02-22 is a valid date.

This really should be part of native Zendesk configuration - A timestamp field is a standard feature of any data model and I believe the ZD database already stores a time component to every date field (albeit 00:00).  Please prioritise this on the backlog.

Hi Jennifer.  The instructions for changing the Agent brand don't work as there is no Subdomain section under Appearance > Branding.  Can you please confirm the  correct process?

Hi Zendesk team.  Do you have an update on the progress of this work please?