Bugzilla Improvements

Bugzilla basically runs Mozilla - it’s core to almost everything we do from tracking core Firefox bugs to tracking Marketing events to operating as our IT ticket queue. Quite simply, we wouldn’t be who we are today without it. With all its greatness, there are quite a few things that don’t quite fit the workflow that is Mozilla, and other bugs that are simply annoying.

So, Schrep asked me to kick off a project to address some of the issues we have with Bugzilla and really invest some time and effort to improve Bugzilla for Mozilla, and the rest of the community. I’ve started by rounding up an initial set of improvements after talking to some of the heavy users within Mozilla, asking for their top complaints and suggestions to improve efficiency in using Bugzilla. Here is what I have come up with.

They gave me plenty of things to work on, but I wanted to open it up to others. I’ve added a section to the bottom of the wiki asking for suggestions - please keep your edits there. If you want to vote up another’s suggestion, just add a +1 to their line. I’ll take the top suggestions/defects and add them into the schedule. Keep in mind we won’t be able to do everything, and are limited in terms of capacity but we are throwing some full time weight behind this to help get this moving.

All our changes are planned to first be applied to BMO, then ported to Bugzilla trunk, so all the code will show up in upstream versions of Bugzilla. We hope to make a difference and move Bugzilla forward in ease of use, performance and innovation.

On a side note, I am looking for community Bugzilla members to help - if you are a Bugzilla developer or know someone who would be willing to help, we’ll take all the help we can get! Contact me at justin at mozilla dot com.

No Comments Yet

You can be the first to comment!

Speak Your Peace

You must be logged in to post a comment.