I have just finished customising the SystemStats,pm and System.pm modules and the SystemStats.dtl file to provide a queue based breakdown of current ticket states for our OTRS setup. Not going to anything with the graphics side as I am not sure that a queue based output would be very usable for our purpose.
My customisation does not break these down by date at moment but I would probably optimise such a query by copying the date constrained result records to an intermediate table and then run queue based or user based queries against the intermediate table for multiple queries. This would probably be a bit more efficient than a single query for each pass. I think to some extent the performance issue could be mitigated by peroidically archiving closed records and storing reporting snapshots. I dont know whether adding specific support for this is on the To Do for OTRS but it could be useful. On Wed, 2003-10-08 at 15:44, Robert Kehl wrote: > On Thursday, October 02, 2003 10:04 AM > Strange, PJ (Philippa) <[EMAIL PROTECTED]> wrote: > >> Is it possible either now or sometime in the near future to have > >> queue specific stats built in to the existing stats offering? > > It were possible right now by hacking otrs/bin/mkStats.pl, and is a > good idea for the future if not already noted somewhere in the > developers' cookbook. > > This is quick'n'dirty'n'hardcoded, but working - you'll get the idea. > Original SQL statement for counting the values, line 210ff: > > my $SQL = "SELECT count(*) FROM ticket_history " . > " WHERE " . > " history_type_id = $State " . > " AND " . > " create_time >= '$Year-$Month-$StartDate 00:00:01'". > " AND " . > " create_time <= '$Year-$Month-$StartDate 23:59:59'"; > _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting f�r Ihr OTRS System? => http://www.otrs.de/
