[ros-bugs] [Bug 3409] New: Bugzilla enhancement

[ReactOS.Bugzilla at www.reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=3409

           Summary: Bugzilla enhancement
           Product: Online Services
           Version: unspecified
          Platform: x86 Hardware
               URL: http://www.reactos.org/bugzilla/
        OS/Version: ReactOS
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: Homepage
        AssignedTo: ros-bugs at reactos.org
        ReportedBy: hto at dev.null
         QAContact: ros-bugs at reactos.org


Looks like resolution "INVALID" is a bit overloaded. It was used when
 - reported bug is not a (reactos) bug (e.g. bug 2989, bug 2028);
 - more info needed (bug 2820, bug 3112);
 - bug report is old (bug 3107, bug 1912, bug 2326, bug 2192);
 - bug is not reproducible (bug 3003);
 - patch not accepted (bug 3265);
 - after major code changes (bug 1577, bug 1866);
 - in other cases.

Remember that "INVALID" defined as "the problem described is not a bug".

Also resolution "FIXED" was used when bug
 - can no longer be reproduced (bug 2223, bug 2306);
 - was "fixed" by hack (bug 2240);
 - really fixed. :-)

What I suggest.
1. Add "INCOMPLETE" resolution.
2. Perhaps yet another resolution ("HACKFIXED"?) means "the bug was fixed, but
there is still some problem that needs to be resolved".
3. More discipline when dealing with bug reports.

BTW, there is no "Bugzilla" component.

References:
1. https://bugzilla.mozilla.org/page.cgi?id=fields.html
2.
http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.