/build/static/layout/Breadcrumb_cap_w.png

K1000 Custom Ticket Rule for moving tickets between queues

I am trying to create a custom ticket rule to move tickets between queues depending on the category the ticket is saved as.  Since my exposure to SQL is limited overall, I found a link (http://www.itninja.com/question/custom-ticket-rule-to-change-queue) from 1/2013 but when I try to use it as the template, it gives me an error as if I am using the incorrect syntax and I am guessing that this may be due to the fact that our appliance is at v5.5.90545.

Any help would be greatly appreciated.  Thank you all.


1 Comment   [ + ] Show comment
  • I ended up using the Wizard for the select query. I looked at that KB article to get the Queues figured out (thanks). The syntax error I was getting was "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near..."

    This error only occurred when I would use select queries that people had posted here that looked like they were prior to v5.5 being available. - mattcollins31 11 years ago

Answers (1)

Answer Summary:
Posted by: Wildwolfay 11 years ago
Red Belt
2

Make sure that you have the correct queue ID's.  You can see this by accessing you kace with /adminUI and seeing what the hd queue id up in the address bar.  If you have your MYSQL Workbench up and running, you can just do a select * from HD_QUEUE and figure out your queue ID's.

 

What is the syntax error you are getting?

 

btw, check this article out:

http://www.kace.com/support/resources/kb/article/Using-Helpdesk-Ticket-Rules-to-transfer-tickets

 

Don't be a Stranger!

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

Sign up! or login

Share

 
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