Another feature idea


#1

Not sure if this has been thought of already. But a really useful feature for
2.0 would be user statistics accesible through the admin interface (along with
perhaps merging the admin functionality into the webrt.cgi module, rather than
having to access a seperate cgi). Its a great feature for large groups where
you want to keep track of who’s doing their job.


#2

Not sure if this has been thought of already. But a really useful feature for
2.0 would be user statistics accesible through the admin interface (along with
perhaps merging the admin functionality into the webrt.cgi module, rather than
having to access a seperate cgi). Its a great feature for large groups where
you want to keep track of who’s doing their job.

Statistics is useful, but I think it makes more sense having it
separately. I think there exists some contributions for making statistics
for 1.0. It should also be easy to pull out statistics from the mysql
command line.

Tobias Brox (alias TobiX) - +4722925871 - urgent emails to
sms@tobiasb.funcom.com. Check our upcoming MMORPG at
http://www.anarchy-online.com/ (Qt) and play multiplayer Spades,
Backgammon, Poker etc for free at http://www.funcom.com/ (Java)


#3

Not sure if this has been thought of already. But a really useful feature for
2.0 would be user statistics accesible through the admin interface (along with
perhaps merging the admin functionality into the webrt.cgi module, rather than
having to access a seperate cgi). Its a great feature for large groups where
you want to keep track of who’s doing their job.

True-- also, the lead sysadmin here thought it might be useful to be able
to print out some sort of “manager’s report” that she could give to her
manager. You know, show how many individual problems we’ve solved in a
given week, show that some users are more “needy” than others, etc.

so perhaps a printer-friendly version might be useful as well.

j.


#4

Statistics would be great if tickets could be ‘weighted’ so as to reflect
that adding a user account is not the same as rebuilding DNS or somesuch.
Unless you weight them someone who does a lot of easy tasks looks great
while someone who is wrestling with the ugly chore that noone else wants
to deal with looks like a slacker. I suppose this could be done with a
’complexity’ field in the database.

A managers report could be done with a Perl script…even graphed. That
would be useful. Graphs always go over well with management :slight_smile:

e.


#5

| Statistics would be great if tickets could be ‘weighted’ so as to reflect
| that adding a user account is not the same as rebuilding DNS or somesuch.
±–>8

Areas and/or queues work nicely for this…

brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]


#6

Statistics would be great if tickets could be ‘weighted’ so as to reflect
that adding a user account is not the same as rebuilding DNS or somesuch.
Unless you weight them someone who does a lot of easy tasks looks great
while someone who is wrestling with the ugly chore that noone else wants
to deal with looks like a slacker. I suppose this could be done with a
’complexity’ field in the database.

Actually, RT 1.1 allows you to specify how long you spend on tickets. I
think that might make a better base for weighted statistics than an
arbitrary complexity field.

I believe that an integrated statistics system would be good for RT and
several people have volunteered to hack on such a thing for 2.0. I’ll try to goad one of them into posting some ideas to rt-devel.

A managers report could be done with a Perl script…even graphed. That
would be useful. Graphs always go over well with management :slight_smile:

e.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – jrvincent@wesleyan.edujesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
This is scary. I’m imagining tracerouting you and seeing links like “Route
84” and “Route 9, Exit 14”. Obviously, this is illness induced.
–Cana McCoy


#7

Jesse [jesse@fsck.com] quoth:
*>>
*>Actually, RT 1.1 allows you to specify how long you spend on tickets. I
*>think that might make a better base for weighted statistics than an
*>arbitrary complexity field.

Well, time doesn’t always equal complexity either, e.g. something that
takes an experienced person 5mins might tax a greenhorn for a couple hours
or more.

Hmm… what about a user profile that could be customised per experience
level? This way if you have a jr admin who took on 2 challenging tasks is
rewarded in the statistics. Just an idea though it’s probably more trouble
than it’s worth.

IIRC Vantive produces statistics but nothing terribly sophisticated, just
user or group and numbers of tickets over a given time period.

e.


#8

I don’t think something like this will be in RT2. I’d be interested to have
someone prototype it after we get 2.0 out, though I’m dubious of it’s utility to effort ratio.

jesseOn Thu, Mar 30, 2000 at 09:53:40AM -0600, Elaine -HFB- Ashton wrote:

Well, time doesn’t always equal complexity either, e.g. something that
takes an experienced person 5mins might tax a greenhorn for a couple hours
or more.

Hmm… what about a user profile that could be customised per experience
level? This way if you have a jr admin who took on 2 challenging tasks is
rewarded in the statistics. Just an idea though it’s probably more trouble
than it’s worth.

IIRC Vantive produces statistics but nothing terribly sophisticated, just
user or group and numbers of tickets over a given time period.

e.

jesse reed vincent – jrvincent@wesleyan.edujesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I’m reasonably sure that at least two of the electric blue kangeroos
I saw were real.