3,267
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + − Line 15:
Line 14: − − VERIFIED and CLOSED: Sugar does not substantially use VERIFIED or − CLOSED. When used, they indicate that a third party has checked to see − that a bug was properly resolved.
→Bug Status
The status field indicates the general status of a bug. What state we are in the life cycle of a bug?
The status field indicates the general status of a bug. What state we are in the life cycle of a bug?
'''UNCONFIRMED'''
'''UNCONFIRMED''' This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have obtained permissions from the BugSquad may confirm this bug, changing its state to NEW. It may also be directly resolved and marked RESOLVED, or more information may be necessary, moving it to NEEDINFO.
This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have obtained permissions from the BugSquad may confirm this bug, changing its state to NEW. It may also be directly resolved and marked RESOLVED, or more information may be necessary, moving it to NEEDINFO.
'''NEW''' This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted and become ASSIGNED, passed on to someone else and remain NEW, or resolved and marked RESOLVED.
'''NEW''' This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted and become ASSIGNED, passed on to someone else and remain NEW, or resolved and marked RESOLVED.
'''RESOLVED''' The bug has been resolved in some way. The resolution field should contain a secondary status describing the way in which it was resolved. See the Resolutions section for more details.
'''RESOLVED''' The bug has been resolved in some way. The resolution field should contain a secondary status describing the way in which it was resolved. See the Resolutions section for more details.
== Resolutions ==
== Resolutions ==