SeaMonkey/Bugzilla-FAQ: Difference between revisions

; ''DUPLICATE'' or ''INVALID'' for accidentally created clones?
(→‎Before you start: (or needing improvement))
(; ''DUPLICATE'' or ''INVALID'' for accidentally created clones?)
Line 59: Line 59:
* For ''RESOLVED - FIXED'': should show the earliest ''SeaMonkey'' version for what the bug has been fixed (known fix). Target information can be used in queries much more effected than the ''Status Flag'' "fixed" to find out with what version a particular problem became solved by a fix.
* For ''RESOLVED - FIXED'': should show the earliest ''SeaMonkey'' version for what the bug has been fixed (known fix). Target information can be used in queries much more effected than the ''Status Flag'' "fixed" to find out with what version a particular problem became solved by a fix.
* For ''RESOLVED - WORKSFORME'' or similar resolution: Shows the earliest ''SeaMonkey'' version behind ''Version'' for what the bug now longer is reproducible (fix unknown)
* For ''RESOLVED - WORKSFORME'' or similar resolution: Shows the earliest ''SeaMonkey'' version behind ''Version'' for what the bug now longer is reproducible (fix unknown)
=== Resolution ===
; ''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 the 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".
Confirmed users
538

edits