Update Monitor articles related to when the user successfull fixes their first data removal
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: jcuevas, Assigned: dgalindo)
Details
Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]
**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.
Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]
Note: If yes, ensure 'Advanced Fields' are visible by selecting 'Show Advanced Field' at the top right, then scroll to 'Security' and check 'Confidential Mozilla Employee Bug (non-security)'.'
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]
Monitor
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
KB content update/ new content
Please provide a summary of the request and outline any user-facing changes. [REQUIRED]
Monitor Plus users will receive an email after their first data removal is fixed.
Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]
yes
Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]
On Train
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
6/19/2024
Does the content need to be published prior to the release date? If so, when? [REQUIRED]
Note: If you don’t let us know if this date changes, it will be published on this date
No
Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]
Note: A minimum of 10 days is required for translation requests.
English Only
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
https://mozilla-hub.atlassian.net/browse/MNTOR-2700
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'
https://www.figma.com/design/CaEKIhvSJqf6KNIMzSkt40/Concepts-for-Monitor-MVP-Redesign?node-id=11736-19025&t=ODuqMgT6VwMrytb8-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.
Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Tony Cinotto
Joe
|
Assignee | |
Updated•1 year ago
|
|
|
Assignee | |
Comment 2•1 year ago
|
||
|
|
Assignee | |
Updated•1 year ago
|
|
|
Assignee | |
Comment 3•1 year ago
•
|
||
|
|
Assignee | |
Comment 4•1 year ago
•
|
||
Released
|
|
Assignee | |
Updated•1 year ago
|
Description
•