New issue
Advanced search Search tips

Issue 924096 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Label Request] Enterprise-Triaged

Project Member Reported by atwilson@google.com, Today (18 hours ago)

Issue description

1] Label Name: Enterprise-Triaged

Guideline 1: Unless a hierarchy of labels is needed, please avoid creating
new root parents.
Guideline 2: Proj(ects) labels should be used for efforts that have a clear
start/ end
Guideline 3: Hotlist labels should be used for tracking on-going efforts
across multiple components (e.g. Hotlist-GoodFirstBug)
Guideline 4: Due to the way auto-complete works we avoid using hyphens to
express anything other than hierarchy (e.g. UI-Browser-Omnibox).  We use
CamelCase to represent multiple words (e.g. Hotlist-CamelCase versus
Hotlist-Camel-Case).


2] Parent Label (e.g. Proj-, Hotlist-, etc...): none

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
label as parents.

3] Description of Label: This label has been used by our enterprise triage process. It is currently on nearly 1200 open bugs, and I'd like to make it simpler for people to work with by having it part of the dropdown/autocomplete.

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently). See go/cros-ent-bug-triage.



 

Comment 1 by hablich@chromium.org, Today (15 hours ago)

Status: Assigned (was: Untriaged)
Can you please elaborate why the status "Unconfirmed" and "Untriaged" do not cover the need? What is the benefit of a new label to tag issues?

Sign in to add a comment