From c041df98fff3687425fbc7fa81c4a096e3919c12 Mon Sep 17 00:00:00 2001 From: Barbara Bermes Date: Thu, 14 Mar 2019 14:40:19 -0400 Subject: [PATCH] Create --telemetry-request.md Added Telemetry template --- .github/ISSUE_TEMPLATE/--telemetry-request.md | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/--telemetry-request.md diff --git a/.github/ISSUE_TEMPLATE/--telemetry-request.md b/.github/ISSUE_TEMPLATE/--telemetry-request.md new file mode 100644 index 0000000000..de446fedc5 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/--telemetry-request.md @@ -0,0 +1,32 @@ +--- +name: " Telemetry User Story" +about: Create a telemetry user story, assigned to an Epic to track telemetry + +--- +Owner: Product Manager + +#### Description & Product Manager / Data Scienties User Story +- As a product owner, I want to know if people type use feature X so I can... + +#### 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](https://github.com/mozilla/data-review/blob/master/request.md) the telemetry + + + + + + +