-
Notifications
You must be signed in to change notification settings - Fork 329
Description
Bug Description
When a user completed the set up of Reader Revenue Manager (RRM) they're redirected to the dashboard and if the organization/publication has a policy violation the appropriate banner notification appears. When the user navigates away from the dashboard and revisits later, the desktop notification appears.
As Mariya mentioned on this Slack conversation:
Generally, it seems too soon to show the second notice after only one click or navigating away from the dashboard. the user has already been notified in the same session (they just saw the post-setup notice), and immediately after they see a notice again. whether critical or of lower priority.
The following was agreed: When RRM is set up and the organization/publication has any level of policy violation, the desktop notification should not appear until the user next logs in to their website. This is to ensure that the UX is not frustrating because of the continuous appearance of the notification until it's dismissed.
Steps to reproduce
- Set up RRM and choose an organization/publication that has any policy violation. (Or use the tester plugin)
- Click on the Complete setup CTA
- You will be redirected back to the dashboard with the appropriate notification
- Navigate away from the dashboard and you will see the appropriate notification straightaway.
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
- When the user sets up RRM with an organization or publication that has any level of policy violation, when they navigate away from the dashboard they should not instantly see the desktop notification.
- The notification should only appear on the dashboard after the user has logged back into their website.