-
Notifications
You must be signed in to change notification settings - Fork 717
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
App Layout: consider low priority rooms filter #7089
Comments
I'd also like a solution to this, as I put rooms in low-priority usually I don't want to deal with when opening the app. Besides bringing back collapsible sections (which I guess was part of the redesign to get rid of?) a toggle in layout preferences to just hide them would be an option. (but maybe also not a great option). |
I think a toggle would be an ok solution but definitely not ideal.
I also think that ideally when searching/filtering rooms these rooms would show up (at the bottom of the list). This way when I am looking for a specific room I don't need to remember if I marked it as low-priority or not. I think the sort-to-bottom with some sort of collapsible section or jump handles these really nicely because they are still there and are obviously included when searching or filtering but don't push out my "Regular Priority rooms". Right now the problem is that the rooms that I talk in often that are often lower volume are getting pushed offscreen by these low priority rooms that I am just in to ask the occasional question, look up something or react to mentions. |
Having an "All except low priority" filtered tab is essential to my workflow. |
Maybe there could be an option to replace the Unreads tab with a Low Priority tab. |
Element might know how useful users think some of the tabs are via analytics. I reckon it would not be too hard to simply let users select which tabs they want instead of the current all or nothing choice. |
There definitely needs to be a way to filter and differentiate between important communications and the less important communications I can get to later.
Why not both? Or maybe even replace "People" with |
A really-really-cool power-user option would be allow tabs to be defined based on a simple filter/expression language. For example I could define High-Priority Unread ordered by room name or Direct Messages ordered by recency. Non-power users would have a few default tabs (just like now) but power-users can adjust the number and types of tabs to match their workflows. |
Your use case
The new layout lists low priority rooms on top when rooms are listed by activity while I want them out of the way of more interesting rooms.
An extra tab will probably make the interface too cluttered and just listing them below the other rooms might put them too far out of reach, so I don't know what the best solution could be.
Have you considered any alternatives?
No response
Additional context
No response
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered: