1,157
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − Inspired by the [http://bugzilla.gnome.org/page.cgi?id=bug-status.html bug status fields from gnome] I would do the following:+ − + − − Line 34:
Line 32: − + Line 43:
Line 41: − + Line 49:
Line 47: − + − + Line 61:
Line 59: + + Line 69:
Line 69: − + Line 76:
Line 76: − + Line 92:
Line 92: − + − + + +
BugSquad/Status Fields (view source)
Revision as of 20:16, 24 February 2010
, 20:16, 24 February 2010moved Walter is a wanker 7/Status Fields to BugSquad/Status Fields over redirect: revert
{{TOCright}}
== Bug Status (Default=Unconfirmed)==
== 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?
'''DUPLICATE''' This bug is filed already in the data base.
'''DUPLICATE''' This bug is filed already in the data base.
== Severity (Default=Normal) ==
== Severity (Default=Unspecified) ==
This field describes the impact of a bug on a user.
This field describes the impact of a bug on a user.
'''Major''' Major loss of functionality - menu item broken, data output extremely incorrect, or otherwise difficult/useless to use
'''Major''' Major loss of functionality - menu item broken, data output extremely incorrect, or otherwise difficult/useless to use
'''Unspecified''' A minor part of the component is non functional or broken
'''Unspecified'''
'''Minor''' minor loss of function, or other problem where easy workaround is present.
'''Minor''' minor loss of function, or other problem where easy workaround is present.
'''Trivial''' Cosmetic problem like misspelled words or misaligned text.
'''Trivial''' Cosmetic problem like misspelled words or misaligned text.
== Priority (Maintainers field) ==
== Priority (Maintainers field, Default=Unspecified by Maintainer) ==
This field describes the importance and order in which a bug should be fixed. This field is ''utilized by hackers'' to prioritize their work to be done. While each term has a description, it is important to note that priority is highly subjective, and bugs can move up or down the priority scale based on subjective questions like 'would we be embarassed to release the software with this bug.'
This field describes the importance and order in which a bug should be fixed. This field is ''utilized by hackers'' to prioritize their work to be done. While each term has a description, it is important to note that priority is highly subjective, and bugs can move up or down the priority scale based on subjective questions like 'would we be embarrassed to release the software with this bug.'
'''Immediate''' This bug blocks development or testing work and should be fixed ASAP, or is a security issue in a released version of the software.
'''Immediate''' This bug blocks development or testing work and should be fixed ASAP, or is a security issue in a released version of the software.
'''Low''' Just not all that important. Rarely used in Sugar.
'''Low''' Just not all that important. Rarely used in Sugar.
'''Unspecified by Maintainer''' This is a field for the maintainer only.
== Type (Default=Defect) ==
== Type (Default=Defect) ==
'''Enhancement''' Request for a new feature or functionality.
'''Enhancement''' Request for a new feature or functionality.
== Sugar Version ==
== Sugar Version (Default=Unspecified) ==
This field describes the version of Sugar that a bug has most recently been found in. This field is used by the Sugar release team and other
This field describes the version of Sugar that a bug has most recently been found in. This field is used by the Sugar release team and other
interested parties to find all bugs in a specific version of Sugar, no matter what program the bug is in. For example, one query can find all Sugar 0.82 bugs, whether they are in sugar-toolkit 0.82.1, browse 100, or sugar-artwork 0.82.
interested parties to find all bugs in a specific version of Sugar, no matter what program the bug is in. For example, one query can find all Sugar 0.82 bugs, whether they are in sugar-toolkit 0.82.1, browse 100, or sugar-artwork 0.82.
updating the product version field - that is still useful for maintainers.
updating the product version field - that is still useful for maintainers.
'''Unspecified''' (Default) This bug is in a module that is not in Sugar, or in an unspecified version of Sugar.
'''Unspecified''' This bug is in a module that is not in Sugar, or in an unspecified version of Sugar.
'''Git as of bug date''' In the recent version from git
'''Git as of bug date''' In the recent version from git
Default: Unspecified by Release Team
Default: Unspecified by Release Team
== Operating System ==
== Distribution/OS ==
This field lists the operating system (distribution) the bug was found on. Debian, Fedora, OLPC...
This field lists the Sugar distribution (operating system) the bug was found on. Fields: Debian, Ubuntu, Fedora, OLPC, Gentoo...
[[Category:BugSquad]]