User:Paulc: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Drupal + QMO + Bugzilla =
= About me =  
Module status, ideas, to-do list, etc.
* Book large screen for presentation to amaze everyone when the dashboard is ready
* Try stats on STATUS, PRIORITY
* Chart/Map generation
* Set up MySQL database + Cron job to sync chosen data
* get bug info from bug list (expand-collapse or AJAX)
** http://drupal.org/project/chart
** http://drupal.org/project/swfcharts
** http://simile.mit.edu/timeplot/
** http://wiki.mozilla.org/Bugzilla:Addons


= Bugzilla feedback =
= Work =  
(sorting...)
;Last changed 6/24
== # of bugs filtered by... ==
Working on QMO.
* Number of unconfirmed bugs over last week
Currently trying to integrate Bugzilla into QMO by fetching data and offering stats, meaningful counts, lists of bugs, etc.
* Number of fixed bugs over last week.
* Number of verified bugs over the last week.
* Count these totals  by looking at both the Firefox Product and the Core Product
* Weekly line chart of number of unresolved qawanted bugs.  Also the current total.
* Weekly line chart of number of bugs submitted verses fixed
* Weekly line chart of number of bugs with the various [sg*] whiteboard flags
* Weekly line chart of number of bugs with crash or topcrash whiteboard flags
* Weekly line chart of total number of unresolved bugs with regression keyword
* Weekly, monthly, qrtly, years numbers for inlitmus*
* Weekly line chart for total number of bugs with inlitmus+
* It would also be nice to track totals of bugs with [sg], [sg:critical], [sg:high], sg:med], [sg:low], [sg:investigate]
* Number of duplicates (perhaps with list of bugs with most duplicates) [chofmann]


== List of bugs filtered by... ==
See [[QA/Community/QMO_Bugzilla]] and [[QA/Community/QMO_Design]] for more info.
* Blocking Bugs filed by the community [marcia] [1]
* Blocking Bugs filed by the QAE team [marcia] [1]
* Bugs that were filed with the "regression" keyword. [marcia]
* For bugs with regression keyword, I'd like a sorted list of all the Firefox and Core components by number of regressions found. [P1-timr!] It would be good to be able to specify the time range for the report.
* Bugs filed per component over the last week.
* Blocking nominations, and blocking + 'd bugs (need more info).  The flags for FFx3 are: blocking-firefox3.1+ and wanted-firefox3.1+. wanted-firefox3.1+ bugs are further broken down by priority P1-P3.
* List of the bugs with the qawanted keyword
* Lists for the various whiteboard strings: inlitmus?, inlitmus-, inlitmus+, crash, topcrash
 
 
[1] one problem here is that our definition for bug markings that mean "blocking" seems to change project to project, or even within various cycles and stages of progress.    getting some standard reports that are really useful might help us to make the set of 'blocking markings' we use more consistant across the projects and development lifecycles, or we need to make that part of the system pretty flexible so a project admin could adjust the queries and reports on the fly... [chofmann]
 
Also see [https://bugzilla.mozilla.org/show_bug.cgi?id=442747 bug 442747]
 
== References: ==
* [http://wiki.mozilla.org/Firefox:3.0_Bug_Charts  Current Bugcharts for FFx3]
* A spreadsheet with groupings of bugzilla components into higher level areas is available from timr.  Jay has similar info from Talkback.

Latest revision as of 17:26, 1 July 2008

About me

Work

Last changed 6/24

Working on QMO. Currently trying to integrate Bugzilla into QMO by fetching data and offering stats, meaningful counts, lists of bugs, etc.

See QA/Community/QMO_Bugzilla and QA/Community/QMO_Design for more info.

Retrieved from "https://wiki.mozilla.org/index.php?title=User:Paulc&oldid=98377"