Confirmed users
538
edits
SeaMonkey/Bugzilla-FAQ: Difference between revisions
Jump to navigation
Jump to search
→Bugzilla fields: Whiteboard
(→How to read User Agent string information: background on the "Gecko" token) |
(→Bugzilla fields: Whiteboard) |
||
| Line 62: | Line 62: | ||
; ''DUPLICATE'' or ''INVALID'' for accidentally created clones? | ; ''DUPLICATE'' or ''INVALID'' for accidentally created clones? | ||
: Sometimes a bug report ends up in the Bugzilla database twice in a row. If you see two bugs with the same summary and adjacent bug numbers, mark one as '''''INVALID'''''. ''DUPLICATE''s are indication that the problem affects many users or appears in different components (or may be the bug description is not optimum). The DUPLICATEs, what might contain important additional information, will have to be included into the Bug proceeding process, and especially when a fix is available it should be tested for all aspects mentioned in the DUPLICATEs. An accidentally created ''clone'' simply is '''INVALID''' and worthless for the bug fixing process. To avoid unnecessary interest for that clone, don't mention it in "See Also" of the remaining Bug report (or anywhere else), only leave a comment in the clone referring to the remaining Bug Report like "Accidentally created clone of Bug 123456". | : Sometimes a bug report ends up in the Bugzilla database twice in a row. If you see two bugs with the same summary and adjacent bug numbers, mark one as '''''INVALID'''''. ''DUPLICATE''s are indication that the problem affects many users or appears in different components (or may be the bug description is not optimum). The DUPLICATEs, what might contain important additional information, will have to be included into the Bug proceeding process, and especially when a fix is available it should be tested for all aspects mentioned in the DUPLICATEs. An accidentally created ''clone'' simply is '''INVALID''' and worthless for the bug fixing process. To avoid unnecessary interest for that clone, don't mention it in "See Also" of the remaining Bug report (or anywhere else), only leave a comment in the clone referring to the remaining Bug Report like "Accidentally created clone of Bug 123456". | ||
== Whiteboard == | |||
Should be used for search strings suitable for ''Bugzilla'' queries. That means ''Whiteboard'' entries should "tag" common characteristics of Bugs with the same Whiteboard entries. For important bug report internal ints (Workaround: see comment 17) pleas use field "User Story" | |||
=== SeaMonkey internal Whiteboard tags === | |||
Please only use for Products with ''SeaMonkey'' in it's name | |||
;[easyconfirm] | |||
: for Bugs suitable for beginners. Report has a good step by step instruction how to reproduce, but still additional information will be required. | |||