I have had the chance to improve the bugzilla SQR in many ways. I have improved the overall run time inside of the ETL (both in kettle and in a python script), fixed a few bugs (A major one that was causing problem with the Open Bug Count), added new dimensions, and constructed a few dashboards. All my changes will be able to be found at sourceforge.
I added a bug severity dimension, added a component level onto the product dimension, added a team level onto the person dimension, and a days dimension to track bugs over a distribution.
I have made some mock up dashboards here and posted bellow are a few snap shots of the charts in them. Tell me what you think and what you would find useful!






SQL, ETL, all sounds very exciting, if only there was some explanation of what it means.
http://lmgtfy.com/?q=ETL
SQR is a tough one. It stands for Software Quality Reports. It was the original name for the project that allows us to generate useful reports on Bugzilla data.
Here you go. ;)