this quarter i’ve been working on redesigning how bugs are viewed and edited on bugzilla.mozilla.org — expect large changes to how bmo looks and feels!

unsurprisingly some of the oldest code in bugzilla is that which displays bugs; it has grown organically over time to cope with the many varying requirements of its users worldwide. while there has been ui improvements over time (such as the sandstone skin), we felt it was time to take a step back and start looking at bugzilla with a fresh set of eyes. we wanted something that was designed for mozilla’s workflow, that didn’t look like it was designed last century, and would provide us with a flexible base upon which we could build further improvements.

a core idea of the design is to load the bug initially in a read-only “view” mode, requiring the user to click on an “edit” button to make most changes. this enables us to defer loading of a lot of data when the page is initially loaded, as well as providing a much cleaner and less overwhelming view of bugs.

major interface changes include:

fields are grouped by function, with summaries of the functional groups where appropriate

fields which do not have a value set are not shown

an overall “bug summary” panel at the top of the bug should provide an “at a glance” status of the bug

the view/edit mode:

allows for deferring of loading data only required while editing a bug (eg. list of all products, components, versions, milestones, etc)

this results in 12% faster page loads on my development system

still allows for common actions to be performed without needing to switch modes

comments can always be added

the assignee can change the bug’s status/resolution

flag requestee can set flags

you can use it today!

this new view has been deployed to bugzilla.mozilla.org, and you can enable it by setting the user preference “experimental user interface” to “on”.