/build/static/layout/Breadcrumb_cap_w.png

Viewing Helpdesk Tickets on Multiple Queues

Is it possible to configure a report to view tickets on multiple queues? I'd assume there is, but how does one create a query for that?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: airwolf 13 years ago
Red Belt
0
Yes, it's actually easier than restricting the report to one queue. All tickets are in the HD_TICKET table, regardless of their queue number.

If you want to restrict to a specific queue, you'd use "WHERE HD_TICKET.HD_QUEUE_ID = 1", specifying the appropriate queue ID. For multiple queues, you'd change "= 1" to "in (1,2)". You can add as many elements to the array as you want - comma separating them. For example, 5 queues numbered 1 through 5 would be (1,2,3,4,5).
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
The wizard does focus on one queue so if you edit the same report in the SQL editor you should be able to find a reference to HD_TICKET.HD_QUEUE_ID = 1 (as airwolf is referring to ) in your existing report and modify that part. The problem is that once you edit the SQL of the report then you can't go back in the wizard and tweak it, but it should be easy enough to make this modification again.

TIP: if you want to keep your original then duplicate the report before you modify it. Also make sure you click "autogenerate layout" checkbox if you change anything
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

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

Sign up! or login

View more:

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