fenix/.github/ISSUE_TEMPLATE/--telemetry-request.md
Divya Raj 073b0ae103 Fixed Issue #3741 - %s in Japanese version + A few typos (#3749)
* Typo in README

* Fixed Issue #3741 - %s in Japanese version

* Fixed various typos
2019-06-28 18:56:25 -05:00

1.2 KiB

name about title labels assignees
📈 Telemetry User Story Create a telemetry user story, assigned to an Epic to track telemetry [Telemetry] Feature:Telemetry

Owner: Product Manager

Description & Product Manager / Data Scientist User Story

  • As a product owner, I want to know if people type use feature X so I can...

Hypothesis

  • We believe this feature is useful to users, and successful when ...

What questions will you answer with this data?

Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

What probes (suggested, if applicable)

Dependencies (Added by PM and Eng)

Acceptance Criteria (Added by PM)

  • Event pings can be queried via re:dash
  • 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
  • NOT an AC: Data science to create dashboard or further graphs (this will be a separate issue, this issue is only about hooking up the events described and that they can be queried in re-dash)