Bugzilla, YUI, and other things.

Tuesday, March 09, 2010

ideas for User stats to gether for more human bugzilla v0

Statistics to show about a user

All things in list with & in the bullet might have a "veteran" and "newbie" designation.

Newbie and Veteran status can be determined either by a count or time.
-- If it is a count then it would simply be an above a line and below a line
-- If it is a time it would be before X date for veterans and newbie would be determined by N duration before today.
-- We might want to allow users to configure these settings and let them use one or both systems.
-- V1 might just have a config file, V2 might have a table in the database or a param tab

* CC List
***& Num bugs user is on CC list

* QA Field
***& Num bugs user is QA on

* Comments
***& Num
*** Recent Activity ( num bugs in the past N duration )

* Bug Fixing
***& Assigned
*** Assigned and Fixed
*** Recent Activity ( num where status was changed to fixed in N duration )

* Bug Patches
***& Num patches created
*** Num patches created with + flag
*** Recent Activity ( patches created in N duration )

* Bug Filing
***& Num bugs filed
*** Num bugs resolved as duplicates
*** Recent Activity

* Bug Reviewer
***& Num reviews per bug
*** Recent Activity ( Num bugs set to + or - in N duration )

* Bugs Verified
*** How do we do this???

What has the user filed bugs on?
-- With all these stats how do we determine what they have worked on?
-- Do a count per project for how many ANY of the above the user has done, if the number is more than N then that person has that project show up

Once the extension is installed we first need to do old stats gathering
After that we will rely on either a cron job OR hooks or both

We need to extend the user object and add these stats


  1. I have thought about this as well periodically over the last few months, and had some really cool ideas that I haven't flushed out.

    One idea is:
    when a user files a bug, find a similar bug (os, hardware, product version, component) that hasn't been verified and have them try to reproduce it. This would be an option on the thank you screen and give us the opportunity to have bug finders spend a few extra minutes and help us validate the onslaught of new bugs.

    Another idea is;
    a facebook application that gives you points for filing, fixing, verifying bugs. This would give the bug finders credibility in their peer network and when their bugs are fixed in a future version they could easily post a link to have their friends install the version of firefox (etc...) that they helped make better.

    The list can go on. This post sort of goes down the same road and it seemed appropriate to share the possibility of more instant gratification techniques with little modifications to our current tools and workflow.

  2. @elvis314 thanks for adding to the list. The facebook app seems cute and fun. The first idea was a Google summer of code project that never quite got finished.