Open Bug 1932458 Opened 21 days ago Updated 20 days ago

Update to Pocket Export article

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: daniela, Assigned: dgalindo)

Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

Yes

Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Pocket

Select the type of request.

KB content update/ new content

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 to https://support.mozilla.org/en-US/kb/exporting-your-pocket-list to inform users of the export caching behaviour: an export gets cached for 30 days. In this time, if a new export is initiated, it will not be updated until the current one expires.

Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

No

Please indicate if this is an on- or off-train release [REQUIRED]

Already released

What is the anticipated release date? [REQUIRED]

Already released

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]

Only languages that it is currently localized in.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

In response to https://mozilla.slack.com/archives/C05F0EZ68KE/p1732052418901869

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Daniela Arcese

Dayani, assigning this update to you. When you have a moment, please create a task link in the Asana Content Roadmap and cross-link it both here and in the roadmap for tracking.

Assignee: nobody → dgalindo
Status: NEW → ASSIGNED
Flags: needinfo?(dgalindo)

Joe's update:
https://app.asana.com/0/0/1208503944090643/f

Joe Cuevas
· 20 days ago
Decision made to get functionality out using existing processes. Team will work on updated experience after the fact. So we may not need to update this KB article just yet.

You need to log in before you can comment on or make changes to this bug.