Bug Triage/Projects/Bug Handling/Triage Rules: Difference between revisions

← Older edit

Bug Triage/Projects/Bug Handling/Triage Rules (view source)

Revision as of 21:55, 6 December 2017

1,245 bytes added , 6 December 2017

m

Emceeaich moved page Bugmasters/Projects/Bug Handling/Triage Rules to Bug Triage/Projects/Bug Handling/Triage Rules: Move to Bug Triage hiearchy.

Emceeaich

Administrators

550

edits

@@ Line 19: / Line 19: @@
 === Say NO early ===
-The thing I really want you to get comfortable with is saying *no* to a bug, especially enhancement requests. If it's something you don't think your team will undertake, seriously consider closing with resolution `WONTFIX`.
+The thing I really want you to get comfortable with is saying '''''no''''' to a bug, especially enhancement requests. If it's something you don't think your team will undertake, seriously consider closing with resolution `WONTFIX`.
 == Decisions ==
 If you have lots of bugs and limited time, look the ones with crash, regression, and security-related keywords first. Follow crash report links and see what versions and how many people are affected.
+{| class="wikitable"
+|-
+! State !! Description !! Notes
+|-
+| btpp-fix-now || Bug is a critical crash or regression that should be fixed before it goes out in a release || Bug needs to be assigned, have release flags set, and set P1
+|-
+| btpp-active || Bug is non-critical, but being worked on as part of a teams' regular iteration || Bug should be assigned
+|-
+| btpp-fix-later || Bug will be worked on soon || Set P2 on the bug
+|-
+| btpp-triage-followup-YYYY-MM-DD || You can't make a decision on the bug, but will by a week from now || Bug should have `needinfo` set or a dependency bug linked
+|-
+| btpp-triage || This bug is not urgent and its final disposition is deferred to the team's triage meeting || If the component doesn't have a standing triage meeting, this option should not be used
+|-
+| btpp-backlog || This is a legitimate bug, you'll accept a patch for it, but there are no plans to work on it || Set P3
+|-
+| btpp-close || On further review, this bug can be closed, or if it's a feature request, WONTFIX'ed || Set status to CLOSED and appropriate resolution
+|}
 === Things you are doing now ===
@@ Line 32: / Line 52: @@
 ;Keywords: crash, topcrash, regression
 ;Words in summary: crash, regression
-;Group restrictions: Security-related-
+;Group restrictions: security-related-
 ;Priority: P1
 ;Comments: links to crash logs, links to specifications
-Check who set the bug's metadata, we don't put keywords, or priority/severity under access control.
+There's no access control in bugzilla on keywords, and priority/severity, so check who set those.
 ;btpp-active: sometimes your team will jump on a bug, or a member of the community is working on it, even if it's not urgent, make sure there's a person assigined, a mentor if it's a volunteer, and release flags.
@@ Line 60: / Line 80: @@
 === [meta] and tracking bugs ===
-For the moment, ignore these.
+Ignore these.
+{{message|The Hello team has two existing triage whiteboard tags which they use: [triage] and [uxtriage].}}
+=== Intermittents ===
+Ignore these.
 === Bugs for your regular triage ===
-If you want to defer a bug to a standing triage meeting, add the whiteboard tag `btpp-triage`. The expectation is that you'll move this bug to another category at your triage.
+If you want to defer a bug to a standing triage meeting, add the whiteboard tag `btpp-triage`. We expect that the bug is not a btpp-fix-now, and that you'll move this bug to another state at your triage.