We upgraded to v1.12.2 yesterday, but now we see some DB Errors in the log.

[SELECT COUNT(DISTINCT CASE WHEN A1.staff_id IN (1) THEN A1.ticket_id END) AS q1, COUNT(DISTINCT CASE WHEN (A1.team_id IN (3, 7) OR A1.staff_id IN (1)) THEN A1.ticket_id END) AS q7, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A1.team_id IN (3, 7) THEN A1.ticket_id END) AS q16, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A1.team_id IN (3, 7) AND A2.state = 'open' AND A1.team_id IN (3, 7) AND A1.staff_id IN (1) THEN A1.ticket_id END) AS q17, COUNT(DISTINCT CASE WHEN A2.id IN (1, 9, 10, 11) AND A1.staff_id IN (1) AND A1.ticket_id = Z1.ticket_id THEN A1.ticket_id END) AS q18, COUNT(DISTINCT CASE WHEN A2.state = 'open' THEN A1.ticket_id END) AS q24, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A2.state = 'open' AND A1.team_id IN (8) THEN A1.ticket_id END) AS q25, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A2.state = 'open' AND A1.team_id IN (7) THEN A1.ticket_id END) AS q27, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A2.state = 'open' AND A1.team_id IN (6) THEN A1.ticket_id END) AS q28, COUNT(DISTINCT CASE WHEN A2.state = 'open' AND A2.state = 'open' AND A1.team_id IN (5) THEN A1.ticket_id END) AS q29 FROM ost_ticket A1 JOIN ost_ticket_status A2 ON (A1.status_id = A2.id) LEFT JOIN ost_thread A3 ON (A3.object_type = 'T' AND A1.ticket_id = A3.object_id) LEFT JOIN ost_thread_referral A4 ON (A3.id = A4.thread_id) LEFT JOIN ost_staff A5 ON (A4.object_type = 'S' AND A4.object_id = A5.staff_id) LEFT JOIN ost_team A6 ON (A4.object_type = 'E' AND A4.object_id = A6.team_id) LEFT JOIN ost_department A7 ON (A4.object_type = 'D' AND A4.object_id = A7.id) WHERE (A2.state = 'open' AND (A1.staff_id = 1 OR A5.staff_id = 1 OR A1.team_id IN (3, 7) OR A6.team_id IN (3, 7))) OR (A2.state IN ('open', 'closed') AND (A1.dept_id IN (1) OR A7.id IN (1)))]

Unknown column 'Z1.ticket_id' in 'field list'<br />

Looks like your custom queue Q18 is borked. Please delete it and re-add it

8 months later

Morning all, apologies for reviving an old thread. I persistently have this error. As suggested removing the offending queue stops the error appearing, but as soon as a user creates a new queue it's back. Any ideas what would be causing this?

Users do not create and cannot create Queues, Only Agents can.
You would have to edit the bad queue to see what it is doing and try to figure out correct it.
Without an example of what the queue is vs what it is supposed to do we would not be much help in fixing it.
Please start a new thread if you would like to dig in and do that and post your specifics. Thanks.

Write a Reply...