From c8c74153b1c47d57570cc1e1da3c290814a3f180 Mon Sep 17 00:00:00 2001 From: Andrew Scott Date: Mon, 20 Jul 2020 09:28:08 -0700 Subject: [PATCH] refactor(dev-infra): Update triage labels documentation (#38081) Add new type: confusing and type: use-case labels to the triage readme as well as clarify that freq and severity are only required for type: bug/fix PR Close #38081 --- docs/TRIAGE_AND_LABELS.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/TRIAGE_AND_LABELS.md b/docs/TRIAGE_AND_LABELS.md index c6fbf95fae..8251812ac3 100644 --- a/docs/TRIAGE_AND_LABELS.md +++ b/docs/TRIAGE_AND_LABELS.md @@ -62,6 +62,8 @@ What kind of problem is this? * `type: feature` * `type: performance` * `type: refactor` +* `type: use-case` +* `type: confusing` ## Caretaker Triage Process (Primary Triage) @@ -83,8 +85,8 @@ Once the primary triage is done, the ng-bot automatically adds the milestone `ne The component owner is responsible for assigning one of the labels from each of these categories to the issues that have the milestone `needsTriage`: - `type: *` -- `frequency: *` -- `severity: *` +- `frequency: *` (only required for `type: bug/fix`) +- `severity: *` (only required for `type: bug/fix`) We've adopted the issue categorization based on [user pain](http://www.lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html) used by AngularJS. In this system every issue is assigned frequency and severity based on which the total user pain score is calculated.