Last modified: 2014-01-03 16:18:08 UTC
The interface is slow to call up tickets, and even slower to complete searches for text inside a ticket... "Search for this text inside the database and show me which tickets match it".
OTRS 2.3.1 added support for fulltext search: http://otrs.org/ Upgrading to that or better and enabling fulltext should make the problem a lot better.
I support this upgrade, and suggest that we find a nice time to implement the change. I will even avail myself on the date in question to help do the upgrade.
Support :)
(In reply to comment #3) > Support :) > *points to "Vote for this bug"* :P
Shh you :)
(In reply to comment #1) > OTRS 2.3.1 added support for fulltext search: > > http://otrs.org/ No, it didn't add support for fulltext search in any traditional sense. It adds an article_search table to index the article table, but it doesn't put any FULLTEXT indexes on it. Instead, it populates it with a list of words contained in each article, separated by spaces, and searches the table with LIKE '%word%'. I'm not sure if the performance improvement would make it worth doing.
Submitted upstream: http://bugs.otrs.org/show_bug.cgi?id=3724
*** Bug 29698 has been marked as a duplicate of this bug. ***
[Removing RESOLVED LATER as discussed in http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html . Reopening and setting priority to "Lowest". For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]
Quick update: This issue is still unresolved in the upstream bugtracker of OTRS.
We rolled out OTRS v3.2.9. Please reopen the ticket or create a new one if the new version suffers this problem.