Confirm, emeritus
882
edits
Changes
m
no edit summary
** As I understand it, the rationale for separating them is that priority is managed by the assignee (together with TM), while severity is not. It was therefore put in the "assignee" block. [[User:GavinSharp|GavinSharp]]
* IMO, the alias in the new header should be enclosed in square rather than round brackets, and perhaps italicised italicized to make it obvious it's not part of the summary text.
* The alias is before the summary in the header but after it in the editing boxes. We should make the two consistent.
* The changes to eliminate the "knob" are non-skin changes; they should be removed in order to make it more obvious what changes he is suggesting that are actually doable in a skin revision.
* I like the dropdown drop-down styling, but it shouldn't apply to the flags - it makes it look as if the flag name can be changed.
* The Reported and Modified dates should either both have seconds, or neither.
* The field title colour color is too light. I see the desire to deemphasisedeemphasize, but this has gone too far. Even a small departure from black can have a noticeable effect.
* Target Milestone -> Target
* Merging Priority and Severity into "Importance" is wrong; if these fields are used correctly, they mean two different things, and need to be labelled labeled as such. It's not obvious from "P1... P5" that it's a priority field.
[[User:Gerv|Gerv]] 07:23, 2 January 2007 (PST)
=== gwagenknecht ===
* Over all, I like the redesign of the show bugs page.
* Having the bug status as the first field is great. But I would like it to be even more prominent (for example, try to leave the cell bellow it empty). (It might be subjective but it's one of my major complaints agains against JIRA. It's not easy enough to ready the bug status. Don't know why but maybe because the UI is too busy for me.)
* I like the ideas exposed by ''dolske'' in [http://people.mozilla.com/~dolske/bugzilla/mockup2.html mockup2]. Especially the right alignment of the field names make it easier to read and the colorization of the input fields makes them easier to recognize.
* Don't know if it would be interesting to have dates formatted as "x hours/days/weeks/months ago" for the modification date. (Could be a user setting though)
* The outlines and icons of form controls add a *lot* of visual complexity to the page. The mockup replaces almost all the HTML controls with just plain text (but you can reactivate the controls by clicking "edit"). This really improves readability, but the obvious cost is having to click "edit" to update fields is annoying. This needs improved.
* The top part of the bug is using CSS3(ish) columns, so you will see 2 or 3 columns depending on how wide the browser is. Or, uhh, 1 column for narrow windows. And browsers that don't support -moz-column-width. There's not much control over where a column starts, so tweaking a design to work with different column counts is tricky (the mockup just happens to look fairly reasonable). Perhaps there are JS/DOM tricks that could help? I consider this a failed experiment as-is.
* The CC list is hidden again (ala mconnermconnor's mockup).
* Combined some fields
