Latest revision as of 09:32, 2 June 2009

These are draft suggestions related to the meanings of various entities in Bugzilla. They will be moved to the appropriate wiki pages if finalized and approved.

How to Triage: Add severity and priority

The following is to be added to the checklist at BugZappers/How_to_Triage (draft pending at User:Beland/How to Triage).

X.) Are the severity and priority set correctly?

See BugZappers/BugStatusWorkFlow for definitions.

BugStatusWorkFlow: Remove duplicate ASSIGNED content

The following is to replace the ASSIGNED section of BugZappers/BugStatusWorkFlow in its entirety:

ASSIGNED

The triage team believes that this is a complete, actionable bug. A triager has used the Triage checklist for NEW bugs; all necessary information has been supplied, and this bug is not a duplicate of an older bug.

BugZappers/BugStatusWorkFlow: Explain all remaining states

(Previous draft material removed; states are explained at: [1])

Severity and Priority

Possible amplification of: https://bugzilla.redhat.com/page.cgi?id=fields.html

Proposal A

Severity is used to describe how serious a bug is in the context of the specific component:

Urgent: Software is completely unusable, loses data, or the RPM won't update properly. Frequent or commonly encountered crashes.
High: Loss of important functionality, or severe usability problem. Infrequent or un-reproducible crashes, or crashes that occur only in specific circumstances.
Medium: Highly visible cosmetic defect, moderate usability problem, loss of minor functionality, moderate loss of functionality with workaround, or high priority request for enhancement. [default choice]
Low: Minor cosmetic defect, minor usability problem, or low priority request for enhancement.

Priority is used to indicate what order bugs should be fixed, in the context of the entire release:

Urgent: Urgent or high severity affecting the majority of users, demanding the immediate attention of an engineer.
High: Urgent or high severity affecting many users; should be at the top of the package maintainer's todo list.
Medium: Medium severity affecting many users, or high severity affecting few users.
Low: Affects a small number of users or is low severity.

Proposal B

Reporter/bug traigers manipulate only with severity of bugs, priority might be originally copied from reporter's setting (alternatively: only triagers and maintainers can change severity once the bug is filed, reporter can set it just when filing the bug):

Urgent: bug makes whole system unusable (or it is a security bug, which is per definition urgent)
High: bug makes the program in question unusable
Medium: real bug which makes program more difficult to use, at least part of the program is available; possibly workarounds are available
Low: rest ... cosmetic issues, corner cases with unusual configurations, etc.

@@ Line 26: / Line 26: @@
 =BugZappers/BugStatusWorkFlow: Explain all remaining states=
-The following is to be added to [[BugZappers/BugStatusWorkFlow]].  This page may need to be renamed.  These explanation are only guesses until refined by the community.
+(Previous draft material removed; states are explained at: [https://bugzilla.redhat.com/page.cgi?id=fields.html])
-==Statuses==
+=Severity and Priority=
-===FAILS_QA===
+Possible amplification of: https://bugzilla.redhat.com/page.cgi?id=fields.html
-An update has been released to fix this bug, but testers rejected the update in Bodhi due to problems.  Further development is needed.
+==Proposal A==
-===RELEASE_PENDING===
+Severity is used to describe how serious a bug is in the context of the specific component:
-???
-==Resolutions==
-===NOTABUG===
-This is not a bug report or enhancement request.  This includes requests for support, user error, etc.
-===WONTFIX===
-The developer or package maintainer has decided that the suggestion is not in the best interest of the software, and will not implement it.  If this conclusion is disputed, the question should be taken to the appropriate development mailing list.
-===DEFERRED===
-???
-===WORKSFORME===
-The bug could not be reproduced, and the maintainer does not know what might be causing it.  The reporter can reopen the bug, but they may need to help identify why it occurs for them but not the person who attempted to reproduce it.
-===CURRENTRELEASE===
-The bug is fixed in the latest supported Fedora release, which is more recent than the one the bug is reported in.  A fix will not be backported due to the limited resources of the Fedora Project.  Users have the option of upgrading to the latest release, or living with the bug.
-===RAWHIDE===
-The bug was reported in Rawhide, and is fixed in the latest daily updates.
-===ERRATA===
-The bug is fixed by an update releases against the same version of Fedora the bug was reported against.
-===DUPLICATE===
-The bug is reporting the same problem as another bug.  Only one bug per issue is kept open until the problem is fixed, and it is not marked as a duplicate.
-===UPSTREAM===
-The Fedora Project is deferring a fix or enhancement to the upstream developers.  A bug should be filed in the upstream tracking system and linked from the Fedora bug.
-In many cases, Fedora simply repackages free and open source software produced by other projects, and does not have the resources to do much beyond that.  In some cases, the decision about whether or not to fulfill a request is best left to the upstream developers, since it impacts all distributions that carry the software, not just Fedora.
-===NEXTRELEASE===
-The bug has been fixed in Rawhide, but reported in a supported release.  The next supported release will contain the fix, at which point users will have the option of upgrading.
-===INSUFFICIENT_DATA===
-The bug has been closed because requested information was not or could not be provided.  Anyone who is able to supply the requested information can re-open the bug.
-== Severity and Priority ==
-Severity is used to describe how bad a bug is for the reporter, in the context of the specific component:
 * Urgent: Software is completely unusable, loses data, or the RPM won't update properly.  Frequent or commonly encountered crashes.
-* High: Loss of important functionality, or usability problem producing major frustration.  Infrequent and un-reproducable crashes.
+* High: Loss of important functionality, or severe usability problem.  Infrequent or un-reproducible crashes, or crashes that occur only in specific circumstances.
 * Medium: Highly visible cosmetic defect, moderate usability problem, loss of minor functionality, moderate loss of functionality with workaround, or high priority request for enhancement. [default choice]
 * Low: Minor cosmetic defect, minor usability problem, or low priority request for enhancement.
@@ Line 99: / Line 45: @@
 * Medium: Medium severity affecting many users, or high severity affecting few users.
 * Low: Affects a small number of users or is low severity.
+==Proposal B==
+Reporter/bug traigers manipulate only with severity of bugs, priority might be originally copied from reporter's setting (alternatively: only triagers and maintainers can change severity once the bug is filed, reporter can set it just when filing the bug):
+* Urgent: bug makes '''whole system''' unusable (or it is a security bug, which is per definition urgent)
+* High: bug makes '''the program in question''' unusable
+* Medium: real bug which makes program more difficult to use, at least part of the program is available; possibly workarounds are available
+* Low: rest ... cosmetic issues, corner cases with unusual configurations, etc.

Search

User:Beland/Bugzilla Legend: Difference between revisions