Patch attached.
And RT’s empire spreads to another entertainment studio. ;]
–j
Jim Meyer, Geek at Large purp@acm.org
initialdata.patch (877 Bytes)
Patch attached.
And RT’s empire spreads to another entertainment studio. ;]
–j
Jim Meyer, Geek at Large purp@acm.org
initialdata.patch (877 Bytes)
Patch attached.
And RT’s empire spreads to another entertainment studio. ;]
–j
p.s. version 3.6.1. =]
Jim Meyer, Geek at Large purp@acm.org
Thanks. AppliedOn Tue, Aug 22, 2006 at 09:36:15AM -0700, Jim Meyer wrote:
Patch attached.
And RT’s empire spreads to another entertainment studio. ;]
–j
Jim Meyer, Geek at Large purp@acm.org
List info: The rt-devel Archives
RT has served me well, we have some 90,000 tickets, in varying queues. I have been asked to start providing
statistics for how many tickets, per queue, we get per week. Is this some standard reporting module I’ve yet
to run across, or should I roll my own?
Check out the rt-count script here:
http://www.cs.kent.ac.uk/people/staff/tdb/rt3/
~JasonOn Tue, 2006-08-22 at 13:42 -0400, Robert Seifer wrote:
RT has served me well, we have some 90,000 tickets, in varying queues. I have been asked to start providing
statistics for how many tickets, per queue, we get per week. Is this some standard reporting module I’ve yet
to run across, or should I roll my own?
List info: The rt-devel Archives
/------------------------------------------------------------------
| Jason A. Smith Email: smithj4@bnl.gov |
| Atlas Computing Facility, Bldg. 510M Phone: +1-631-344-4226 |
| Brookhaven National Lab, P.O. Box 5000 Fax: +1-631-344-7616 |
| Upton, NY 11973-5000, U.S.A. |
------------------------------------------------------------------/
Robert,
There is an add-in called RTx::Statistics, but I haven’t been able to
update it in awhile, and there are reports that it doesn’t work properly
with 3.6, although I believe that at least one person was able to get it
to work.
More information:
http://wiki.bestpractical.com/index.cgi?RT3StatisticsPackage
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh@mqsoftware.com
RT has served me well, we have some 90,000 tickets, in varying
queues. I have been asked to start providing
statistics for how many tickets, per queue, we get per week. Is
this some standard reporting module I’ve yet
to run across, or should I roll my own?
If you’re running a RT in the 3.6 series, you have some reporting
functionality built in – see ‘Reports’ under ‘Tools’ in the main menu.
You may find py Request Tracker Report download | SourceForge.net useful. Works
for us on RT3.0.2.On Tue, 2006-08-22 at 13:42 -0400, Robert Seifer wrote:
RT has served me well, we have some 90,000 tickets, in varying queues. I have been asked to start providing
statistics for how many tickets, per queue, we get per week. Is this some standard reporting module I’ve yet
to run across, or should I roll my own?
List info: The rt-devel Archives
Regards
Theo
We use jpgraph, a php module, with a modified version of the main
page. It’s kind of a pain sifting through the RT MySQL tables though.
AlexOn Aug 24, 2006, at 3:50 AM, Theo Kramer wrote:
You may find py Request Tracker Report download | SourceForge.net useful.
Works
for us on RT3.0.2.On Tue, 2006-08-22 at 13:42 -0400, Robert Seifer wrote:
RT has served me well, we have some 90,000 tickets, in varying
queues. I have been asked to start providing
statistics for how many tickets, per queue, we get per week. Is
this some standard reporting module I’ve yet
to run across, or should I roll my own?
List info: lists.bestpractical.com Mailing Lists
rt-devel
–
Regards
Theo
List info: lists.bestpractical.com Mailing Lists
rt-devel
Any idea why the Time to Resolve (scatter graph) doesn’t work while the
others works fine? I already installed the Apache::GD::Graph 0.96 and add
these lines in httpd.conf
<Location /Statistics>
Sethandler perl-script
Perlhandler +Apache::GD||Graph
Does it something to do with FastCGI?
—rommie