KACE Product Support Question

Is there a field in the DB that tracks where a ticket in a queue originated from?

03/02/2017 620 views
I would like to have a "Ticket Source" field that automatically is populated on ticket creation with the appropriate source of the ticket creation, whether the web UI or email, with a custom ticket rule.  However I don't know if that attribute is even tracked in the DB (or possibly already available in a default field I am missing) and would appreciate if someone could point me in the right direction if it is?

Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

There isn't one field that tracks this, but it is possible by comparing some values from the HD_TICKET and the HD_TICKET_CHANGE tables, specifically the first change for the ticket.

If HD_TICKET_CHANGE.VIA_EMAIL is set then the ticket was created via email, otherwise it was created via the UI. 

You can also compare who created the ticket with the possible owners to get an idea of whether or not an end user created the ticket or if it was created by a technician.

If you are creating tickets with a custom rule then those are probably coming in via email, and you can check to see what the value of VIA_EMAIL is in those cases. Presumably only tickets coming from that email address were created via rule.

Using that information you should be able to create ticket rules that will set your custom field appropriately.
Answered 03/03/2017 by: chucksteel
Red Belt

  • Awesome. Thanks for taking the time, it's greatly appreciated.

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