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

Issue 620947 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Feature



Sign in to add a comment

Add a new metric for "unknown language" different from INITIATION_STATUS_LANGUAGE_IS_NOT_SUPPORTED

Project Member Reported by juliecattiau@google.com, Jun 17 2016

Issue description

We should log separately "unknown language" and "unsupported language". Currently everything is logged under the same metric and it represents a large proportion of cases.

See userflow for details: https://docs.google.com/drawings/d/1sensdEa18hNsW0ok-KPn8X5LyWwil3hNcVEQ6HBzSRY/edit
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 17 2016

Labels: Hotlist-Google

Comment 2 by ftang@chromium.org, Jun 29 2016

Status: Assigned (was: Untriaged)

Comment 3 by ftang@chromium.org, Jun 29 2016

Components: UI>Browser>Translate
Labels: Hotlist-Translate
Owner: napper@chromium.org

Comment 5 by napper@chromium.org, Apr 18 2017

Owner: amoylan@chromium.org
Status: WontFix (was: Assigned)
This breakdown already exists under the separate metric Translate.UnsupportedLanguageAtInitiation.
Components: -UI>Browser>Translate UI>Browser>Language>Translate

Sign in to add a comment