[Telemetry] Update notice message#158669
Conversation
|
Documentation preview: |
|
Pinging @elastic/kibana-core (Team:Core) |
|
Pinging @elastic/kibana-docs (Team:Docs) |
src/plugins/telemetry_management_section/public/components/telemetry_management_section.tsx
Outdated
Show resolved
Hide resolved
src/plugins/telemetry_management_section/public/components/telemetry_management_section.tsx
Outdated
Show resolved
Hide resolved
src/plugins/telemetry_management_section/public/components/telemetry_management_section.tsx
Outdated
Show resolved
Hide resolved
...anagement_section/public/components/__snapshots__/telemetry_management_section.test.tsx.snap
Outdated
Show resolved
Hide resolved
src/plugins/telemetry_management_section/public/components/telemetry_management_section.tsx
Outdated
Show resolved
Hide resolved
|
@gchaps, thank you for your comments. I'll address them today and update the screenshots with the new content. |
jloleysens
left a comment
There was a problem hiding this comment.
Great work @afharo ! Did not test locally, but the test coverage looks great.
Thanks for adding the screenshots. WDYT about making the status of usage collection bold or italicised?
packages/core/saved-objects/core-saved-objects-api-server/src/saved_objects_repository.ts
Outdated
Show resolved
Hide resolved
| optIn: null, | ||
| }, | ||
| }); | ||
| expect(telemetryService.config.userCanChangeSettings).toBe(true); |
There was a problem hiding this comment.
unrelated to this PR and non-blocker: is there a reason config is exposed on the telemetryService? Seems that the useCanChangeSettings is the same value just synced from config?
There was a problem hiding this comment.
yeah... there is/was a bit of a nightmare config vs. satinized config (especially for the optIn value, where we differentiate the actual value and the expected behaviour, and both are used in different places)...
We def need to revisit this. I bet we can remove many of the public APIs in this service 😇.
| telemetryService.getUserShouldSeeOptInNotice = getUserShouldSeeOptInNotice; | ||
| const telemetryNotifications = mockTelemetryNotifications({ telemetryService }); | ||
| expect(telemetryNotifications.shouldShowOptedInNoticeBanner()).toBe(false); | ||
| telemetryNotifications['optInStatusNoticeBannerId'] = 'bruce-banner'; |
src/plugins/telemetry/public/services/telemetry_notifications/telemetry_notifications.test.ts
Outdated
Show resolved
Hide resolved
…saved_objects_repository.ts Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
…telemetry_notifications.test.ts Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
@jloleysens, I went with italics because it serves the purpose of catching the eye when reading the message. Bold felt like bringing attention from any place on the page (interrupting other onboarding flows). Please, let me know if you prefer it bold. |
|
@afharo thanks for sharing that. It's a question that invites deep philosophical reflection and product thinking 😄 To help answer the question I would ask: how much attention do we want to draw to this? For me I'd want users to be maximally aware and so lean toward bold as this is a good way to draw attention to softer grey text that is already de-emphasised. OTOH, we might also choose to leave it as is (regular weight, not italicised). But that is the product part of the question. Bolding that status might lead to more users opting-out. |
|
@jloleysens I pinged @cdanderson98 (from legal) to let us know his thoughts. Also pinging @arisonl (PM) and @gchaps (docs) to complete the different POVs 😇 |
|
Probably, @elastic/kibana-design also has something to say here. WRT the discussion of highlighting the current status of telemetry (enabled/disabled) in bold, or italics, or none. |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsasync chunk count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @afharo |
|
I don't want to delay the important update that PR brings in terms of the text we show to our users, so I created the follow-up issue #158841 to discuss whether we prefer bold or italics 😇 |
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com> (cherry picked from commit 312ba3a)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.8`: - [[Telemetry] Update notice message (#158669)](#158669) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2023-06-01T15:53:02Z","message":"[Telemetry] Update notice message (#158669)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"312ba3a758a05cea2d490a5174838cd84ac2cc8d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Team:Core","Feature:Telemetry","release_note:skip","backport:prev-minor","v8.9.0"],"number":158669,"url":"https://github.com/elastic/kibana/pull/158669","mergeCommit":{"message":"[Telemetry] Update notice message (#158669)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"312ba3a758a05cea2d490a5174838cd84ac2cc8d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158669","number":158669,"mergeCommit":{"message":"[Telemetry] Update notice message (#158669)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"312ba3a758a05cea2d490a5174838cd84ac2cc8d"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>




Summary
This PR revisits the message shown in the opt-in/out status notices/disclaimers/banners in Kibana.
Usage datain favor ofUsage collection(related to @gchaps' comment [DOCS] Telemetry settings: improve phrasing #158396 (comment))How does it look?
Welcome page
When enabled (default):

When disabled:

Notice banner
When enabled (default):

When disabled:

Advanced settings
When enabled (default):

When disabled:

Before the first review
Welcome page
When enabled (default):

When disabled:

Notice banner
When enabled (default):

When disabled:

Advanced settings
When enabled (default):

When disabled:

Checklist
For maintainers