Prototype dashboard for QA Bugzilla queries through Solr

RESOLVED FIXED in Unreviewed


Mozilla Metrics
Frontend Reports
8 years ago
6 years ago


(Reporter: dre, Assigned: Nelson)





(4 attachments)

Want a dashboard that shows several drillable facet lists, an extra filter query box, one chart and one table.

Each facet list will show the items with a count in parenthesis beside it.
Some facets will use the option to display entries that don't match the query with a 0 as the count.  Some won't.
When you click on a facet entry, it will add that item to the query to filter.

Products  (Default selected is Firefox)
Target Milestones

To ease requirements for the dashboard and allow easier demonstration, below the facet lists, we should put a small text box that will allow the user to add conditions to the query (so we can add blocking flag conditions and such if needed for demo purposes)

The top chart should be the "Open Bugs by Day" chart.
Line chart with three lines
X axis is the last 15 days
A. # of bugs entering the open state on this day
B. # of bugs leaving the open state on this day
C. # of bugs that ended the day in the open state "Net Open"

The table is just another facet breakdown by assignee showing the top N assignees with an Others entry and the number of bugs assigned to each.  The entries should be drillable just like normal facets.


8 years ago
Assignee: nobody → nelson.sousa
Created attachment 473603 [details]
Updated schema including flags and target_milestone

This is the updated version of the schema (I’ll put data online for this later today, at a different URL). It includes flags and target_milestone and some changes to the facts/measurements (see next comment).
This is actually a snippet from a java source file in the SVN,
but hopefully I’ll make a Wiki page on this before I leave.


 * How long has the bug been OPENED before being CLOSED or OPENED before 
 * being (re-)OPENed. Use it to obtain the (average) time bugs stay OPENED
 * before being closed.
 * This is -1 for the first version of a bug.

 * How long has the been in the previous status? This is <tt>null</tt> for 
 * the first version and for versions where the status did not change.
 * Use it to obtain metrics such as the average time bugs stay UNCONFIRMED.
 * This is -1 for the first version of a bug.

 * How long has the bug been OPEN/CLOSED, also counting the current version?
 * Useful to get an impression on how long the "current" bugs have been open.
 * For the latest version of a bug, this field is -1 to indicate that it is
 * not available (yet). All we know is that the true value will be *at least*
 * NOW-modification_date.
 * So whenever you get a min of -1 in a solr stats query, you might want to
 * exclude the current bug state (expiration_date:[* TO NOW]).
 * :TODO:
 * In some scenarios it might be desired to get day counts for the latest 
 * bug state (e.g. to answer the question "how old are our bugs"). AFAIK the
 * only way this can be done is using date faceting on the modification_date,
 * which will give counts for specific intervals. That is usually much more
 * useful than calculating an average.

 * How long has the bug been in the current status, also counting the current 
 * version?
 * This -1 for the latest bug version (see above).

 * How long has a bug been OPEN in total (including this version).
 * This is -1 for the latest version (see above).

/** How often has the bug been reopened (so far)? Defined for all versions.*/
Just to be clear comment 2 is only about the measures, not the facets.
Also in the first comment it should of course be 

...OPENED before being CLOSED or *CLOSED* before being (re-)OPENed...
Group: mozilla-stats

Comment 4

8 years ago
The dashboard was completed at the very last minute, and using a lot of components that are not stable enough to go into production. But you can check the staging version at 


Navigate through the menus to select products, components, etc. and the bug counts (numbers in parenthesis in each menu), chart and table will update automatically.

I'm closing the bug. New requests for bugzilla dashboards can be submitted on new bugs.
Last Resolved: 8 years ago
Resolution: --- → FIXED
Very cool that you got something going; thanks!  Firefox is not finding that hostname for me, even if I add or, and I'm on the "Mozilla" wireless network, so I should presumably have access to the intranet sites.  Suggestions?

Comment 6

8 years ago
Hey Dan, 

you need to be connected to the MPT vpn
Ah, ok.  Thanks!
Thanks again for the awesome work!

About the open bugs graph:
1) It should probably read "opened" bugs (that’s what my query tried to do).
2) The query I gave you for that has an error. It does not only give you newly
opened bugs, but also gives you all versions for each bug after creating it, up
to the first time the status changes (e.g. to NEW, ASSIGNED etc).

To work around this, it would be nice if you added a condition, from:

days_in_previous_status:[* TO -1] ...


days_in_previous_status:[* TO -1] (annotation:CREATED*initial* OR annotation:CREATED*0\ activities*) ...

Important: don’t quote the terms. I tried that, but wildcard terms are
different from phrase terms in Solr.

I shall extend the search schema to contain a boolean field "is_first_version"
to make this easier and more efficient.

Comment 9

8 years ago
Created attachment 483264 [details]
Bugzilla_ QA  1 of 3

Comment 10

8 years ago
Created attachment 483265 [details]
Bugzilla_ QA  2 of 3

Comment 11

8 years ago
Created attachment 483267 [details]
Bugzilla_ QA  3 of 3
Target Milestone: Urgent → Unreviewed
You need to log in before you can comment on or make changes to this bug.