442
edits
(→Goal: blech) |
(→Data Continuity: updates) |
||
| Line 3: | Line 3: | ||
* Complete the executive dashboard with both v2 and unified telemetry | * Complete the executive dashboard with both v2 and unified telemetry | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1175583 tracking ticket] | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=1175583 tracking ticket] | ||
** [https://docs.google.com/document/d/1VzQHfzfA-S_lO2wpXDFjDzSJntJCMwP03TzefIj7RrE/edit#heading=h.69zh7w46tg7s working doc | ** [https://docs.google.com/document/d/1VzQHfzfA-S_lO2wpXDFjDzSJntJCMwP03TzefIj7RrE/edit#heading=h.69zh7w46tg7s working doc] | ||
* Complete the search retention report with [https://bugzilla.mozilla.org/show_bug.cgi?id=1199458 both v2 and unified telemetry] | * Complete the search retention report with [https://bugzilla.mozilla.org/show_bug.cgi?id=1199458 both v2 and unified telemetry] | ||
* Revisit the longitudinal/experiment use cases and make sure we have a reasonable way to access the data for those cases | * Revisit the longitudinal/experiment use cases and make sure we have a reasonable way to access the data for those cases | ||
| Line 10: | Line 10: | ||
==Goal== | ==Goal== | ||
To be sure the transition from FHRV2 to Unified Telemetry happens in a predictable way that meets company needs. | To be sure the transition from FHRV2 to Unified Telemetry happens in a predictable way that meets company needs. | ||
===Scope=== | ===Scope=== | ||
| Line 16: | Line 16: | ||
==Duration== | ==Duration== | ||
plan is wrap and present to executives on october 13th | |||
edits