## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each) **Choose one below and delete others. [REQUIRED]** Firefox for Android ## Select the type of request. KB content update/ new content In-product link request ## Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED] Add a SUMO article that can be pointed to from the new preference to "Automatically Send Crash Reports," so that users can make an informed decision on whether to toggle on or off. It should include: * What data is included in a crash report * How we use crash reports * How users can choose to send a crash report or not (we should include both information on the setting to automatically send and details on what happens if that settings is turned off - we ask after a crash if we can send a report) ##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED] Yes. There will be a new option added to settings to "Automatically Send Crash Reports" which includes a "Learn More" link that points to this article ## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED] All regions & locales ## Please indicate if this is an on- or off-train release [REQUIRED] Yes ## What is the anticipated release date? [REQUIRED] 135 ## Does the content need to be published prior to the release date? If so, when? [REQUIRED] No ## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED] Yes, all locales ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] https://mozilla-hub.atlassian.net/browse/FXDROID-2910 ## Please include links to any design assets, visuals, figma files, etc. [REQUIRED] Design for setting: https://www.figma.com/design/a0vLe1jbZMVNBbL3pxBBo7/Settings%3A-ToS---DAU-Opt-out?node-id=6447-12616&t=HCy9nIfIpT42SJa5-4 ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] ## Does the content need approval before publishing? If yes, identify the one approver responsible for this task. Yes. It will need sign-off from Jennifer Johnson (legal), Bobby Holley (project sponsor), TBD engineer, Ashley Thomas
Bug 1931083 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each) **Choose one below and delete others. [REQUIRED]** Firefox for Android ## Select the type of request. KB content update/ new content In-product link request ## Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED] Add a SUMO article that can be pointed to from the new preference to "Automatically Send Crash Reports," so that users can make an informed decision on whether to toggle on or off. It should include: * What data is included in a crash report * How we use crash reports * How users can choose to send a crash report or not (we should include both information on the setting to automatically send and details on what happens if that settings is turned off - we ask after a crash if we can send a report) ##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED] Yes. There will be a new option added to settings to "Automatically Send Crash Reports" which includes a "Learn More" link that points to this article ## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED] All regions & locales ## Please indicate if this is an on- or off-train release [REQUIRED] Yes ## What is the anticipated release date? [REQUIRED] 134 ## Does the content need to be published prior to the release date? If so, when? [REQUIRED] No ## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED] Yes, all locales ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] https://mozilla-hub.atlassian.net/browse/FXDROID-2910 https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0 ## Please include links to any design assets, visuals, figma files, etc. [REQUIRED] https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0 ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] ## Does the content need approval before publishing? If yes, identify the one approver responsible for this task. Yes. It will need sign-off from Jennifer Johnson (legal), Bobby Holley (project sponsor), TBD engineer, Ashley Thomas
## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each) **Choose one below and delete others. [REQUIRED]** Firefox for Android ## Select the type of request. KB content update/ new content In-product link request ## Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED] Add a SUMO article that can be pointed to from the new preference to "Automatically Send Crash Reports," so that users can make an informed decision on whether to toggle on or off. It should include: * What data is included in a crash report * How we use crash reports * How users can choose to send a crash report or not (we should include both information on the setting to automatically send and details on what happens if that settings is turned off - we ask after a crash if we can send a report) ##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED] Yes. There will be a new option added to settings to "Automatically Send Crash Reports" which includes a "Learn More" link that points to this article ## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED] All regions & locales ## Please indicate if this is an on- or off-train release [REQUIRED] Yes ## What is the anticipated release date? [REQUIRED] The article can launch in 134 or 135. Feature will launch in 134, but learn more links may not be added until 135 unless ready earlier ## Does the content need to be published prior to the release date? If so, when? [REQUIRED] No ## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED] Yes, all locales ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] https://mozilla-hub.atlassian.net/browse/FXDROID-2910 https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0 ## Please include links to any design assets, visuals, figma files, etc. [REQUIRED] https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0 ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] ## Does the content need approval before publishing? If yes, identify the one approver responsible for this task. Yes. It will need sign-off from Jennifer Johnson (legal), Bobby Holley (project sponsor), TBD engineer, Ashley Thomas