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
As a user with multiple servers/spaces connected, you do not see notification indicators directly per server.
They are hidden in a dropdown: Screenshot https://i.ibb.co/wcD1MBZ/Bildschirmfoto-2022-02-01-um-14-03-09.png
Also a user needs to click twice if he/she has multiple servers connected.
e.g. in Slack there is a small sidebar, on the far left, to give users a quick overview of their "servers"/spaces and also a notification element per space.
I agree - I consider this a bug since it was introduced in version 5.0 and worked fine before.
In previous versions, the notification indicator was plainly connected to a server. Now, it's just some servers notification and a user must click the dropdown menu to determine the source (server) of the notification): a loss of functionality.
Agree, the switch button for multiple servers is a real pain.
I don't see the interest to add more clics for users, the previous method with tabs was perfect.
Sorry for the ironic tone, but: multiplying clicks seems to be the name of the game here. Already having several teams to follow means that I have to click through all of them, just to understand which channel is the message in.
It would be greatly beneficial if there was an option to see all new messages sorted by time, regardless of the team they come from.
As a user with multiple servers/spaces connected, you do not see notification indicators directly per server.
They are hidden in a dropdown: Screenshot https://i.ibb.co/wcD1MBZ/Bildschirmfoto-2022-02-01-um-14-03-09.png
Also a user needs to click twice if he/she has multiple servers connected.
e.g. in Slack there is a small sidebar, on the far left, to give users a quick overview of their "servers"/spaces and also a notification element per space.
You can upvote this feature it in the Mattermost feature idea forum 👍
The text was updated successfully, but these errors were encountered: