SUMO update to reflect: "App Exclusions" revamp to enable app suggestions
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: sandrigo, Assigned: dgalindo)
References
Details
Product
Mozilla VPN
Select the type of request
Need to update article https://support.mozilla.org/en-US/kb/split-tunneling-app-permissions since we are introducing a new UI that can (potentially) show suggested apps to exclude.
Details are in this bug:
https://mozilla-hub.atlassian.net/browse/VPN-4412
Mocks are here:
https://www.figma.com/file/UZYzma7hlcfE5ke3z8jGbN/App-exclusions-suggestions?type=design&node-id=0-1&t=uEwrgRX8GH16hSIx-0
Is the content embargoed (yes or no)?
No
What current go-to-market plans, timelines, or milestones exist?
No timeline for this at this point, but please monitor VPN-3892.
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases.
VPN-4412
Please add instructions for testing or links to any design assets or visuals.
See Jira ticket.
Does the content need to be localized in any languages outside of our priority locales (yes or no)?
Same language as all other Mozilla VPN Knowledge Base content
Does the content require legal review (yes or no)?
No
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
FYI that I've added a small change to the scope:
In passing, we are updating the name of the feature from "App Exclusions" to "Exclude Apps". We should update relevant KB entries to reflect this.
I made a mistake filing this bug since I mentioned to monitor bug VPN-3892 (which did go live), but in reality this functionality is described in VPN-4412 and is not yet live.
As a result, the article: https://support.mozilla.org/en-US/kb/split-tunneling-app-permissions mentions the Suggested App Exclusions functionality (which is not yet launched) and calls the feature "Excluded Apps" when it's currently called "App Exclusions".
Can we roll that back please? This bug continues to be valid, but the go-live of this change should follow the fate of the VPN-4412 epic. More concretely, the version in which we flip this on, which is tracked on VPN-5763.
Assignee | ||
Updated•9 months ago
|
Description
•