Desktop Onboarding Telemetry Tracking: Difference between revisions
Jump to navigation
Jump to search
Full Query
| Line 18: | Line 18: | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"whiteboard":"[]", | "whiteboard":"[onboarding-telemetry]", | ||
"status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"], | "status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"], | ||
"include_fields":["id", "summary", "status", "target_milestone", "priority", "resolution", "assigned_to", "qa_contact"] | "include_fields":["id", "summary", "status", "target_milestone", "priority", "resolution", "assigned_to", "qa_contact"] | ||
Revision as of 09:57, 31 October 2017
Overview
In order to enhance further desktop onboarding users' experience, telemetry is definitely a good choice to collect useful data.
Below are bugs tracked by [meta] bugs of Desktop Onboarding Telemetry mechanism.
Onboarding Telemetry
Live search result on Bugzilla
12 Total; 3 Open (25%); 9 Resolved (75%); 0 Verified (0%);