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

Issue 894914 link

Starred by 1 user
Status: Assigned
Owner:
█ ushesh@chromium.org
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Define process for making changes to core metrics

Project Member Reported by ushesh@google.com, Oct 12 
Summary of action item:

- Define process, communications, etc
- Ensure we A/B test before rolling out changes

Comment 1 by tdres...@chromium.org, Oct 30 

We don't actually want to A/B test here, we want to ship a separate metric first.

Any progress here?

Comment 2 by ushesh@google.com, Nov 8 

goto/metrics-update-proces

Comment 3 by benhenry@google.com, Jan 10 

This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.

Comment 4 by benhenry@google.com, Jan 10

Status: Untriaged (was: Accepted)

Comment 5 by benhenry@google.com, Jan 11

Labels: Pri-2
Issue has a component, but no priority. Updating to have default priority (Pri-2)

Comment 6 by benhenry@google.com, Jan 11

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