RT Ticket Summary
Will Coleda
around to generate this small report. I'd appreciate feedback on whether
or not something like this would be useful (and suggestions for other things
to report on are welcome.)
If we can settle on a desired set of criteria to report on, Robert says he can
make a more efficient (and accurate) version of the report, as he has direct
access to the RT API. (I'm doing a lot of grepping through plain text
renderings of ticket summaries, which is, of course, evil.)
Parrot Ticket Summary
There are currently 277 new/open tickets.
The oldest ticket was created on: 12Dec2001 [#192]
The average (mean) age of tickets is: 63 weeks
Platforms
All: 1 cygwin: 3 freebsd: 3
Linux: 3 MacOS X: 2 mswin32: 5
os2: 1 other: 2 Unspecified: 252
vms: 1 Win32: 7
Languages
BASIC: 1 tcl: 4 Unspecified: 272
James Mastros
> Robert has provided me access to the RT command line tool, which I scripted
> around to generate this small report. I'd appreciate feedback on whether
> or not something like this would be useful (and suggestions for other things
> to report on are welcome.)
>
> If we can settle on a desired set of criteria to report on, Robert says he can
> make a more efficient (and accurate) version of the report, as he has direct
> access to the RT API. (I'm doing a lot of grepping through plain text
> renderings of ticket summaries, which is, of course, evil.)
>
A list of all bugs at least a week old with no replies.
A list of all bugs at least two weeks old not either solved or marked
wontfix or wishlist. (That are against the current release.)
A list of all bugs of unknown reproducibility against the current
release. (I'm not sure how to formulate this one.)
The current one gives us pretty useless numbers. The current batch
tells us, basically, that most stuff isn't specified in any meaningful
way (perhaps we should make RT smart enough to figure out the platform
from the myconfig, and promote to platform=all as approps).
Perhaps have a pair of keywords or a data item for "has been made into a
test", and we should provide a list of bugs that have not been marked
that way, and also have not been marked as "can't make into a test".
-=- James Mastros
