Change Details

This ticket involves the work of implementing the instrumentation required to track how people are engaging with the Tone Check UX. Per [offline discussion](https://wikimedia.slack.com/archives/G01625LGGQZ/p1750445738073359), the instrumentation required to do the above was added as part of the Multi-Check feature implementation (T352092). As such, this ticket largely holds the work of verifying the ` ===Requirements` have been implemented as expected. === Requirements - `action-accept` - `action-reject` - `check-shown-presave` - `check-shown-midedit` NOTE: @MNeisler to finish populating the section above with all of the events we expect to be logged and the action(s) that will caused them to be logged. === Progress **Next steps** - [ ] !!doing!! Megan to finish populating requirements - [ ] David to confirm instrumentation is implemented - [ ] Esther to QA - [ ] Megan to QA === Done - [ ] Editing QA verifies `===Requirements` are being logged client-side - [ ] @Mneisler verifies `===Requirements` are being logged server-side

This ticket involves the work of implementing the instrumentation required to track how people are engaging with the Tone Check UX. Per [offline discussion](https://wikimedia.slack.com/archives/G01625LGGQZ/p1750445738073359), the instrumentation required to do the above was added as part of the Multi-Check feature implementation (T352092). As such, this ticket largely holds the work of verifying the ` ===Requirements` have been implemented as expected. === Requirements | feature | action | meaning | editCheck-tone| action-accept | User clicks button to accept tone check | editCheck-tone | action-reject | User clicks button to reject tone check | editCheck-tone | check-shown-[moment]| Indicates whether the check was shown pre-save or mid-edit. An event will be sent for every tone check shown. | editCheckDialog | window-open-from-check-[moment]| Indicates when the sidebar to present edit checks was shown === Progress **Next steps** - [x] Megan to finish populating requirements - [ ] David to confirm instrumentation is implemented - [ ] Esther to QA - [ ] Megan to QA === Done - [ ] Editing QA verifies `===Requirements` are being logged client-side - [ ] @Mneisler verifies `===Requirements` are being logged server-side

This ticket involves the work of implementing the instrumentation required to track how people are engaging with the Tone Check UX. Per [offline discussion](https://wikimedia.slack.com/archives/G01625LGGQZ/p1750445738073359), the instrumentation required to do the above was added as part of the Multi-Check feature implementation (T352092). As such, this ticket largely holds the work of verifying the ` ===Requirements` have been implemented as expected. === Requirements - `| feature | action-accept` | meaning - `| editCheck-tone| action-reject`accept | User clicks button to accept tone check - `c| editCheck-shown-presave`-tone | action-reject | User clicks button to reject tone check - `check-shown-midedit` NOTE: @MNeisler to finish populating the section above with all of the events we expect to be logged and the action(s) that will caused them to be logged.| editCheck-tone | check-shown-[moment]| Indicates whether the check was shown pre-save or mid-edit. An event will be sent for every tone check shown. | editCheckDialog | window-open-from-check-[moment]| Indicates when the sidebar to present edit checks was shown === Progress **Next steps** - [ ] !!doing!!- [x] Megan to finish populating requirements - [ ] David to confirm instrumentation is implemented - [ ] Esther to QA - [ ] Megan to QA === Done - [ ] Editing QA verifies `===Requirements` are being logged client-side - [ ] @Mneisler verifies `===Requirements` are being logged server-side