Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark all as read feature #708

Open
facundofc opened this issue Apr 27, 2021 · 9 comments
Open

Mark all as read feature #708

facundofc opened this issue Apr 27, 2021 · 9 comments

Comments

@facundofc
Copy link

Hi there! For me it would be very useful to have a key combination and/or command to mark all unread messages as read. We use Mattermost at work, and so I'd use this when returning from a weekend or holidays. At such situations the unread messages predate pretty much every channel we have, and it's awfully time consuming to review them all.

So, I fallback to hitting ALT+A repeatedly, which is slow and boring. Having a command to do the equivalent of that would be awesome (I think a command is more appropriate here so as to prevent one from performing that action inadvertently).

Thanks!

@jtdaugherty
Copy link
Member

Thanks for the request. Would you expect this to work for just the currently-selected team, or all teams? (I would be a bit wary of marking all channels as read for all teams, but I don't know if you're in a ton of teams.)

@facundofc
Copy link
Author

Hi Jonathan, thanks for considering this request!

We don't use the teams feature in the organization I'm at now, so I wouldn't really know. From what I was able to grasp from quick google searches, I get that the channels' and direct chats' list shows only those belonging to your current team. Hence, you could have a lot of unread messages in channels not currently displayed. If that is really the case, I'd lean towards just marking as read messages on the currently-selected team. I usually prefer shortcuts and commands to act on things I can see on the screen at the moment I input them. This is just my opinion though.

Cheers!

@jtdaugherty
Copy link
Member

Okay, thanks! That makes sense.

@kquick
Copy link
Collaborator

kquick commented Apr 27, 2021

Actually, there's a slight wrinkle to the above: if you have a direct-message channel to a user and that user is a member of both teams, that channel is visible when you are viewing either team.

Would you expect this clear operation to apply to only to group channels, or would you also expect it to clear direct channels, @facundofc ? I would think that we might want this to only apply to the former, but what are your thoughts?

@jtdaugherty
Copy link
Member

Yeah, I was thinking about that, too. I don't think "mark all as read" should skip DM channels, personally. I also don't think it will be weird to make them as read in one team and then see them read in another. The users are server-wide, not team-specific. (Although I forget whether there is a server setting or preference that constrains the listed users to just members of the current team.) My personal preference is for any command or keystroke for this feature to mark all visible channels as read, including DM channels.

@facundofc
Copy link
Author

facundofc commented Apr 27, 2021 via email

@jtdaugherty
Copy link
Member

Thanks for writing that up, @facundofc!

@jtdaugherty
Copy link
Member

Reading over this now, it occurs to me that part of the work on this should include investigation of how the official clients behave, if they support this feature at all.

@NeilHanlon
Copy link

Hiya - I'd love to see this feature too. I don't think the official clients have a 'mark all as read' feature, but they certainly allow you to clear the unread flag on a channel without actually reading the history. This is also especially useful when travelling and with low bandwidth. Ideally, the unread state could be optionally syncronized between matterhorn and other clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants