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

6 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 ==
@@ Line 56: / Line 56: @@
 ;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 81: / Line 81: @@
 Ignore these.
+{{message|The Hello team has two existing triage whiteboard tags which they use: [triage] and [uxtriage].}}
 === Intermittents ===
@@ Line 89: / Line 91: @@
 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.
-{{message|The Hello team has two existing triage whiteboard tags which they use: [triage] and [uxtriage].}}