New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 894912 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Clearly define which metrics must follow formal update process

Project Member Reported by ushesh@google.com, Oct 12

Issue description

Summary of action item:

- List all metrics and order in terms of priority. Based on this, determine which metrics are required to follow this process.

- Find appropriate stakeholders and make sure they are in agreement with their metric being required to follow the defined process.

- Candidates include heartbeat metrics and all metrics in speed launch metrics survey (https://docs.google.com/document/u/1/d/1Ww487ZskJ-xBmJGwPO-XPz_QcJvw-kSNffm0nPhVpj8/edit#heading=h.2uunmi119swk)
 
This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.
Status: Untriaged (was: Accepted)
Labels: Pri-2
Issue has a component, but no priority. Updating to have default priority (Pri-2)
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment