Feed on
Posts
Comments

Update: Bugzilla SQR

August 14th, 2009 by

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!

3 Comments »

3 Responses to “Update: Bugzilla SQR”

  1. on 15 Aug 2009 at 2:27 am   Mossop

    SQL, ETL, all sounds very exciting, if only there was some explanation of what it means.

  2. on 15 Aug 2009 at 9:32 am   deinspanjer

    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. ;)

  3. on 31 Jan 2011 at 5:45 am   Dave Neary

    Hi Mossop,

    I wrote an article on the language of BI: http://blogs.gnome.org/bolsh/2011/01/26/the-ladybird-guide-to-business-intelligence/

    ETL = Extract (data from a data source), Transform it (to a different/useful form), and Load it (into target data storage). Typically this means getting data from CSV files/screen scrapes/a database, ensuring you match inputs to output fields in the target database, and storing the resuling data.

    SQR is just a customised set of reports using the data structures found in Bugzilla and JIRA.

    Dave.

Trackback URI | Comments RSS

Leave a Reply

You must be logged in to post a comment.