The notification panel allows you to mark notifications as read in different ways (you can click on the notification to get to the content, click the "X" or the "mark all as read" action), but it does not allow to make a read notification to become unread again.
Allowing to mark read notifications as unread again makes sense to highlight there is pending work to be done (e.g., the user is planning to reply to a message) when the notification panel is used to organise the wiki work to be done.
If we support the notification model described in T114357 "Mark as unread" is presented as a secondary action for those notifications that are read (check T114357 for more details on secondary actions).
For messages, marking as unread turns the notification to the same status it was before. The notification badge is updated but not highlighted in blue (since the notification is not new). As with any other unread notification, it can become read by opening the notification, we can add a "Mark as unread" action for those notifications that are read.marking it as read using the "X" or using the "mark all as read" action.
(Further design details to be decided...)For alerts, marking as unread keeps the notification as unread even if the panel is opened/closed multiple times afterwards. Unread notifications will appear on top even if more recent notifications appear (similar to what happens in messages where unread bock is always at the top). A special close action is provided to (a) communicate that the notification has been "fixed" and (b) allow to mark it as read.
**Additional considerations****Further aspects to observe**
- If we areAfter providing a "mark as unread" for read items, should we provide the opposite action for support for marking as unread notifications?, That symmetrywe may make sense but we needwant to consider how to better integrate with the existing mechanisms to mark items as read.observe the user behaviour to determine the following:
- This, as described, only makes sense for messages since alerts get- Should we provide also a secondary action for "mark as read as soon as" to keep their panel is open. symmetry? AlternativelyWe didn't considered as part of the initial ticket since there are already multiple ways to mark as read, for alerts we could avoid those notifications explicitly marked as unread to become automatically read when the panel is open. In that case we may want to have additional considerations (e.g.,but we want to check if users are expecting to find it also as a secondary action.
- Should we differentiate more the behaviour between alerts and messages? mark them as pinned to clarify the difference in behaviour) which probably deserve its own ticket. If we find that "marking as unread" is not enough to explain why alerts don't get unread automatically we may want to surface that more explicitly.