3,267
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + − * 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.+ − * ASSIGNED: This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED.+ − * NEEDINFO: More information from the reporter is needed to proceed further in fixing this bug. This should not be used when someone needs more information from a developer- a NEW or ASSIGNED bug implicitly needs more information from the developer.+ − * 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.+
→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:''' 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.
'''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.
'''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.
'''ASSIGNED''' This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED.
'''NEEDINFO''' More information from the reporter is needed to proceed further in fixing this bug. This should not be used when someone needs more information from a developer- a NEW or ASSIGNED bug implicitly needs more information from the developer.
'''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.
VERIFIED and CLOSED: Sugar does not substantially use VERIFIED or
VERIFIED and CLOSED: Sugar does not substantially use VERIFIED or