Bugzilla:Bug Layout Revision: Difference between revisions

← Older edit

Bugzilla:Bug Layout Revision (view source)

Revision as of 00:11, 17 April 2007

4,597 bytes added , 17 April 2007

→‎gerv

Hacksaw

16

edits

@@ Line 18: / Line 18: @@
 * Target Milestone can be shortened to Target. Milestone is both Mozilla-specific and obsolete.
+** Milestones are hardly Mozilla specific. That's a standard business term. Target Milestone exactly conveys what this blank should contain. [[User:Hacksaw|Hacksaw]]
 * Right-alignment of the field names would give a better two-column effect and direct the eye to the important information, because I think people look to the right of vertical lines (e.g. ruled margins).
@@ Line 48: / Line 49: @@
 * 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)
 --[[User:Gwagenknecht|Gwagenknecht]] 07:22, 2 January 2007 (PST)
+=== gekacheka ===
+<b>1. Conflicting Criteria for design: use style independent of grouping?</b>
+* Group related fields by assessment task:
+** Assess status:  Status, Keywords, Whiteboard, Depends on, Attachment Flags, Flags
+** Assess importance: Severity, Keywords.   Priority.  Blocking.  Flags.
+** Assess urgency: Severity, Target, Flags, Blocking.
+** Assess interest: Votes, CC
+** Assess module: Product, Component, Summary, Description/Comment
+** Assess reproducibility:  Description/Comment, Attachments, URL, Product, Version, OS, Hardware [hw rare?]
+* Identify who may normally edit fields (e.g., avoid lay commenters editing priority, target)
+** Interested party:  CC, Votes, comments.
+** Reporter/Triager/Confirmer:  any except Priority, Target., Assignee, QA, Flags
+** Module owners, Assignee:  any including Priority, Target, Assignee, QA, Flags
+Ideas:
+* separate assignee/QA fields into group or column associated with QA.
+* identify group of reserved fields with <span style="border: 2px solid black">border</span> or <span style="background: silver">shaded background</span>. (like in paper forms)
+<b>2. Attachments table: consistent location of type</b>
+The type of the attachment should be in a consistent location so
+it is easy to scan for attachments of a particular type.
+For example, sometimes I want to quickly find all the image
+attachments among all the other attachments (say for UI review).  Currently attachment type is placed
+after the title, so its location varies wildly from row to row
+depending on the length of the title.  <br>
+Example of problem:<br>
+    <blockquote><b><u>Zip of files exhibiting issue</u></b> <small>(29.44KB
+application/octet-stream)<br>
+-01-01 11:23 UTC <u>Artie Boss</u></small><br>
+      <u><b>Toolkit patch</b></u> <small>(21.43KB patch)<br>
+-01-01 12:34 UTC <u>Cody Smith</u></small><br>
+      <u><b>Add native Mac theme code, update windows code</b></u> <small>(67.57KB
+      <br>
+patch)<br>
+-01-01 13:45 UTC <u>Cody Smith</u></small><br>
+      <u><b>Possible approach on windows</b></u> <small>(2.38KB
+image/gif)<br>
+-01-01 23:45 UTC <u>Artie Boss</u></small><br>
+      <u><b>Updated patch</b></u> <small>(21.44KB patch)<br>
+-01-01 23:56 UTC <u>Cody Smith</u></small><br>
+    </blockquote>
+Suggestion:<br>
+Place it on the second line.  Right justify variable length
+contributor's name before fixed-length date<br>
+<blockquote>
+  <table width="90%">
+  <tr><td><b><u>Zip of files exhibiting issue</u></b></td></tr>
+  <tr><td><table width="100%" style="margin: 0px"><tr><td><small>(29.44KB application/octet-stream)</small></td><td style="text-align:right"><small><u>Artie Boss</u> <u>2007-01-01 11:24 UTC</u></small></td></tr></table></td></tr>
+  <tr><td><u><b>Toolkit patch</b></u></td></tr>
+  <tr><td><table width="100%" style="margin: 0px"><tr><td><small>(21.43KB patch)</small></td><td style="text-align:right"><small><u>Archie Tek (vacationing until Sept)</u> <u>2007-01-01 12:34 UTC</u></small></td></tr></table></td></tr>
+  <tr><td><u><b>Add native Mac theme code, update windows code</b></u></td></tr>
+  <tr><td><table width="100%" style="margin: 0px"><tr><td><small>(67.57KB patch)</small></td><td style="text-align:right"><small><u>Cody Smith</u> <u>2007-01-01 13:45 UTC</u></small></td></tr></table></td></tr>
+  <tr><td><u><b>Possible approach on windows</b></u></td></tr>
+  <tr><td><table width="100%" style="margin: 0px"><tr><td><small>(2.38KB image/gif)</small></td><td style="text-align:right"><small><u>Artie Boss</u> <u>2007-01-01 23:45 UTC</u></small></td></tr></table></td></tr>
+  <tr><td><u><b>Updated patch</b></u></td></tr>
+  <tr><td><table width="100%" style="margin: 0px"><tr><td><small>(21.44KB patch)</small></td><td style="text-align:right"><small><u>Cody Smith</u> <u>2007-01-01 23:56 UTC</u></small></td></tr></table></td></tr>
+  </table>
+</blockquote>
+<b>3. "Product" link to product descriptions</b>
+Suggest "Product" link to page with product descriptions, such as https://bugzilla.mozilla.org/enter_bug.cgi?full=1 to explain obscure product names such as 'core', 'NPSR', etc.
+[[User:Gekacheka|Gekacheka]] 09:50, 13 January 2007 (PST)
 == Mockups ==
@@ Line 64: / Line 136: @@
 * Not shown: fields that are modified should change their background color to a light-red to indicate the modification.
+--[[User:Jmdesp|Jmdesp]] 07:15, 29 January 2007 (PST) <br/>
+I like your mock-up, but is there a way to make it degrace more gracefully under IE6 ? The form controls changes don't seem to work under it. Also I think it's better not to remove the edit link after it's pressed
 == Summary of discussion prior to 26-Dec-2006 upgrade ==