Znuny Open Source Ticketsystem

i got 4229819, for the first few months there are no problems. As of the moment there are no dynamic fields on AgentTicketSearch and I can't think of any relationship between the attributes on search with dynamic fields. Although don't like my temporary crude fix, I implemented it anyway. I added a ...

EXG133 I already disabled the statistics module however i'm still seeing these queries. I'm still tracing where are the users navigating to execute that query.

I already enabled slow query log of mysql thats why I identified the queries causing the congestion. I traced it to function HistoricalValueGet of Kernel/System/DynamicFieldValue.pm(?), and some certain scripts at kernel/System/DynamicField/Driver. My problem now is where are the users navigating on...

Thanks for the inputs. However upgrade is out of the options at the moment due to the numerous customization done. I would just like to know on which specific part of OTRS requires a query that SELECT all values on dynamic_field_value. If you can help me identify where is that module then I will eit...

Im using OTRS 4.0.6 and I'm having problems with slow query congestion which will then need database restart. I am using around 10 dynamic field values on ticket creation. This is the query in Kernel/System/DynamicFieldValue.pm which registers most of the slow queries. "SELECT DISTINCT($ValueTy...

update: enabled case sensitive search in Config.pm and the slow queries are now using indexes, LOWER() function in particular does not use index.

Yes mysql is configured with innodb plugin, and ticket has proper indexes. I enabled slow query log and these are the long running queries: 1. SELECT DISTINCT(xml_key) FROM xml_storage WHERE xml_type = 'Stats'; (213s) 2. SELECT login , first_name, last_name, email FROM customer_user WHERE ((login = ...

I'm having problems with my MySQL server frequently getting stuck on Ticket Search Queries, using 100% CPU of the database server and OTRS will be unresponsive. TicketSearch.pm: SELECT COUNT(DISTINCT(st.id)) FROM ticket..... Found these queries to be 5 minutes and still running. Any advise would be ...

Thank you for the response. I'll upgrade as soon as possible.

I want to restrict users from viewing other users ticket in a single queue. I haven't found any similar topic on this forum and I only saw ACL implementation on google searches. Is there a way to do it rather than creating dedicated queues to group?

I am using OTRS 3.1.7