/build/static/layout/Breadcrumb_cap_w.png

Custom report organized by queue.

I'm trying to make a report that shows a yearly number of tickets submitted and organized by queue. We're trying to pinpoint which queues get the most tickets submitted to them over the course of the year. Anyone have any ideas?

2 Comments   [ + ] Show comments
  • Are you looking for the initial queue for the ticket or the resulting queue? In our case, we want the resulting queue as the bulk of our tickets are created by our student aides in our Help Desk queue and forwarded to other queues as appropriate. - grayematter 10 years ago
    • The initial queue should work for what I'm looking to do with it. We have our users submitting their own tickets a majority of the time and want to identify the most used queues. - kharrison 10 years ago
      • Though, the resulting queue could work as well. I'd just need to look at the output to say for sure. - kharrison 10 years ago
  • I've been able to modify the 30 day default report for closed tickets to show me tickets for the year and give me the queue id, but I've yet to figure out how to link that back to queue name. - kharrison 10 years ago
    • You need to add a join to the HD_QUEUE table:
      JOIN HD_QUEUE on HD_QUEUE.ID = HD_TICKET.HD_QUEUE_ID

      You can then select HD_QUEUE.NAME for the queue's name. - chucksteel 10 years ago
      • Thanks for the solution. My syntax was apparently off on joining the table. - kharrison 10 years ago

Answers (0)

Be the first to answer this question

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