Time to Resolution / Time to Closure

[Kevin Benton]

Drat - I forgot to add to my original comments - I would like a change to
the DB to add bug_ttr and bug_ttc to the bugs table.  Those fields would
default to zero, then get updated as the bug hit a resolved or closed
status.

---
Kevin Benton
Perl/Bugzilla Developer
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have received
this communication in error, please notify the sender, then destroy any
remaining copies of this communication.
 
 

> -----Original Message-----
> From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org]
> On Behalf Of Joel Peshkin
> Sent: Monday, February 07, 2005 9:28 AM
> To: developers at bugzilla.org
> Subject: Re: Time to Resolution / Time to Closure
> 
> Kevin Benton wrote:
> 
> > My employer is looking for a number of improvements in the reporting
> > capabilities of Bugzilla. One key feature they're asking for is
> > TTR/TTC. It seems to me that adding this kind of feature will help win
> > more support from managers not only at AMD, but at other companies as
> > well as this type of reporting helps demonstrate engineer performance.
> >
> > I've heard it said that "giving back performance reports isn't part of
> > the core functionality of Bugzilla" at this time. I think that this is
> > one reason why some companies may not want to use Bugzilla as much as
> > they could otherwise use it. Many companies that are process and
> > performance focused look specifically for tools that can give them
> > these very types of reports. I know that here, performance reports
> > help us tremendously. I believe that certain types of performance
> > reports ought to be reconsidered like this one, if for no other reason
> > than to win more support from management levels, not just engineers
> > who like Bugzilla as a tool.
> >
> > ---
> >
> >
> Kevin,
> 
> It is useful. If you'll write it... I'll review it. Just don't over-rely
> on the activity log, it is not a journal that can always be smoothly
> rolled back.
> 
> -Joel
> 
> 
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=kevin.benton@amd.com>