This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Telemetry] Voice Search #10465
Labels
E2
Estimation Point: easy, half a day to 2 days
eng:qa:verified
QA Verified
Feature:Search
Feature:Telemetry
Feature:Voice
Projects
Comments
vesta0
added
🙅 waiting
Issues that are blocked or has dependencies that are not ready
and removed
needs:triage
Issue needs triage
labels
May 7, 2020
This is waiting on the feature to be developed first #1216 |
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
May 19, 2020
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
May 19, 2020
sblatz
removed
the
🙅 waiting
Issues that are blocked or has dependencies that are not ready
label
May 19, 2020
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
May 19, 2020
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
May 20, 2020
sblatz
added a commit
that referenced
this issue
May 20, 2020
Hi, verified as fixed on the latest |
data-sync-user
changed the title
[Telemetry] Voice Search
FNX2-15966 ⁃ [Telemetry] Voice Search
Jul 30, 2020
data-sync-user
changed the title
FNX2-15966 ⁃ [Telemetry] Voice Search
FNX-4303 ⁃ [Telemetry] Voice Search
Aug 10, 2020
data-sync-user
changed the title
FNX-4303 ⁃ [Telemetry] Voice Search
FNX3-13915 ⁃ [Telemetry] Voice Search
Aug 10, 2020
data-sync-user
changed the title
FNX3-13915 ⁃ [Telemetry] Voice Search
FNX-4303 ⁃ [Telemetry] Voice Search
Aug 11, 2020
data-sync-user
changed the title
FNX-4303 ⁃ [Telemetry] Voice Search
FNX2-15966 ⁃ [Telemetry] Voice Search
Aug 11, 2020
data-sync-user
changed the title
FNX2-15966 ⁃ [Telemetry] Voice Search
[Telemetry] Voice Search
May 18, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
E2
Estimation Point: easy, half a day to 2 days
eng:qa:verified
QA Verified
Feature:Search
Feature:Telemetry
Feature:Voice
FYI I don't believe we need a DS JIRA request for this one since it's a pretty straightforward event ping.
Description & Product Manager / Data Scientist User Story
As a Product Manager, I want to know how often our users choose to use voice search, so I can determine the importance of this use case in addressing a user need, and prioritize future voice features accordingly.
What questions will you answer with this data?
How often users use voice search by interacting with the new nav bar mic?
Do users choose to turn this feature off in settings?
Acceptance Criteria
Event pings can be queried via re:dash
Event pings can be queried via amplitude
We are sending telemetry events for the actions listed in the requirements
We have documented the telemetry
We have asked a data steward to review the telemetry
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: