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
When a channel has many 'unread' messages, I would like to mark the entire channel as 'read'. This works fine with the 'mark all as read' 'little cross' in the top-right for 'regular' messages, but this doesn't clear unread messages that are inside of threads.
Why would you like to do it?
To get back to 0 unread-message markers without having to separately open all threads with unread messages.
How would you like to achieve it?
I think it would make sense if the 'mark all as read' button would be shown also if there are unread messages in threads, and also mark those as read.
Have you considered any alternatives?
No response
Additional context
This is a duplicate of #1042 which was closed because this issue was supposedly "already fixed on develop and will be fixed in the next release", however there have been many releases since and the behavior is still the same. Most recently tested on version 1.11.40.
The text was updated successfully, but these errors were encountered:
Your use case
What would you like to do?
When a channel has many 'unread' messages, I would like to mark the entire channel as 'read'. This works fine with the 'mark all as read' 'little cross' in the top-right for 'regular' messages, but this doesn't clear unread messages that are inside of threads.
Why would you like to do it?
To get back to 0 unread-message markers without having to separately open all threads with unread messages.
How would you like to achieve it?
I think it would make sense if the 'mark all as read' button would be shown also if there are unread messages in threads, and also mark those as read.
Have you considered any alternatives?
No response
Additional context
This is a duplicate of #1042 which was closed because this issue was supposedly "already fixed on develop and will be fixed in the next release", however there have been many releases since and the behavior is still the same. Most recently tested on version 1.11.40.
The text was updated successfully, but these errors were encountered: