You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It is quite a frustrating experience to go back and mark each unread notification as read after one has already taken action on the associated request or comment. For example, if I click on an unread notification for a review on an sr and ack that request, the "Mark as read" button at the top right corner of the page disappears. I have to go back to the list of unread notifications, find the notification corresponding to the request I just acked and mark it as read manually.
Describe the solution you'd like
Automatically mark the notification as read if one clicks on it and visits the corresponding sr, project, or package page. This would make it similar to how github handles unread notifications and reduce a lot of spurious work just pruning through the list of unread notifications.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It is quite a frustrating experience to go back and mark each unread notification as read after one has already taken action on the associated request or comment. For example, if I click on an unread notification for a review on an sr and ack that request, the "Mark as read" button at the top right corner of the page disappears. I have to go back to the list of unread notifications, find the notification corresponding to the request I just acked and mark it as read manually.
Describe the solution you'd like
Automatically mark the notification as read if one clicks on it and visits the corresponding sr, project, or package page. This would make it similar to how github handles unread notifications and reduce a lot of spurious work just pruning through the list of unread notifications.
The text was updated successfully, but these errors were encountered: