32
edits
Changes
some thoughts from a random b.m.o user
Otherwise I agree with what has been said by the others.
=== Napolj2 ===
I'd move Assignee and QA Contact to just above the CC list, as they all fall under the same conceptual category as "People involved with this bug." Then I'd put Priority, Severity, and Target Milestone in with Status/Resolution, Keywords, and Whiteboard, as they fall under the category of "What state is this bug in". The remaining group of Product, Component, Version, Hardware, and OS, describes this category of "Where this bug occurs."
Ideally, URL should just be considered a type of attachment and not a whole separate field (though this would require converting all the existing URL fields for existing bugs into new attachments, and perhaps patching Bugzilla).
When you have a large amount of dependencies/blocking bugs, you can end up with one column being significantly longer that the other, as in [https://bugzilla-test.mozilla.org/show_bug.cgi?id=300030 the reflow refactoring bug]. (Maybe this won't be an issue since b.m.o has lots of flags too). Perhaps you could allow the dependency/block lists to span both columns? This can be done by moving them to a second TR (with colspan=3) within the outer TABLE.
I'd widen the attachments table to match whatever width the comments are line-wrapped at (or the width of the comment headers), for visual consistency.
The bug description and number are in 3 places, including the page TITLE. I Like how MConnor does the header, with no bug-specific information in it.
The voting links and first/last/prev/next links should be moved into the Actions bar to save space. Actually, those navigation links are useless to me, since I always open bug links from a search into new tabs.
