QA/Community/QMO Bugzilla

From MozillaWiki
< QA‎ | Community
Jump to: navigation, search

Drupal + QMO + Bugzilla

Module status, ideas, to-do list, etc.

Bugzilla feedback

(sorting...)

# of bugs filtered by...

  • Number of unconfirmed bugs over last week
  • 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...

  • 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 bug 442747

References:

  • 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.

Paul C's notes

Documentation:

My humble attempt to document this module is at QA/Community/QMO_Bugzilla/Documentation. Most of the code documentation is in the code itself. The above shows usage.

To-do:

  • per chart:
    • (minor) emulate Bugzilla boolean chart search

How to use - Steps:

  • Enable module
  • Configure basics
    • Main tag, Inner tags
    • List bugs URL
  • Add charts
    • Set basic info
    • Add queries
      • Mapping
      • Url
      • Parameters (later) - emulate Bugzilla boolean chart search

Graph type:

  • Timeplot
    • multiple queries = multiple plots on same graph
    • total count of query results over time range
    • count stored on cron run
    • time range of chart
    • period (data point)
    • list of bug ids for each time period + button "List bugs" using show_bug
    • CB for branch on values + TA for mapping => equivalent to multiple queries
  • Bar chart
    • multiple queries = multiple bars
    • total count of query results
    • count stored on cron run
    • CB for branch on values + TA for mapping => equivalent to multiple queries

Storage:

  • Entity: Query
  • Fields: URL, bug id's as CSV, count


CB = checkbox, TA = textarea

Older stuff:

  • Basic config
    • Which tags to parse (ttp)
    • What's the main tag
    • # of pages/add page using step 9 at http://drupal.org/node/262422
    • cron job (periodically/sync first time)
    • cron job periodical url
    • cron job first time url
  • Graph $i config
    • ttp config:
      • alias (display name)
      • list of values and group values
      • line chart vs pie chart
      • each period vs cumulative chart
      • (optional) parameters
      • (optional) ...
    • ttp mapping/grouping
      • map multiple fields to display label, based on value
      • possibly add multiple display labels (path label style)
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Community/QMO_Bugzilla&oldid=106361"