How can I backdate a new ticket in the service desk?

Howdy all,

Say there's an incident on a Saturday night that I'm responsible for.  However I'm not able to log the ticket till Monday.  Is there any way I can backdate the ticket to that Saturday when I log the ticket Monday morning in the KACE Service Desk?  Hopefully this can be done withing the configuration of KACE and not have to get down and dirty with SQL.

Many Thanks

0 Comments   [ + ] Show comments

Answers (3)

Posted by: Hobbsy 1 month ago
Red Belt

In short yes....and no, there is now way to change  that date on the UI, as that prevents data being questionable.

If you want to change the date you will have to create a ticket rule to just set that single data value in the HD_TICKET table

Posted by: wakeside917 1 month ago
Senior White Belt

Thank you for the answer.  Could you walk me through doing that?

Posted by: Hobbsy 1 month ago
Red Belt

Please Use this advice with caution, you can seriously mess with your KACE database using ticket rules

Create a ticket rule and set a unique title.

Set the SELECT Statement as follows


Where the HD_TICKET ID contains the ticket number you wish to update, this rule will then only update a single record

Set the UPDATE Statement to

update HD_TICKET
    set HD_TICKET.CREATED = (TIMESTAMP ("2021-05-15 14:00:00"))
  where (HD_TICKET.ID in (<TICKET_IDS>))

Enter the TIMESTAMP as the created date that you wish the ticket to have in the format (YYYY-MM-DD HH:MM:SS)

Run the ticket rule and the created date should be set to that date in the single ticket record

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ