-
Notifications
You must be signed in to change notification settings - Fork 13.1k
[NEW] Threads V2 with improved UI and new options #17416
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
Conversation
…/new-threads * 'develop' of github.com:RocketChat/Rocket.Chat: [FIX] Bot Agents not being able to get Omnichannel Inquiries (#17404) [FIX] Allowing blocking a user on channels (#17406) Fix moving-to-a-single-codebase link in README (#17297) Regression: Fix mem usage with more than one argument (#17391)
|
Looking at After screen and I don't think that threads panel should hover the main screen and ability to read other messages in the channel in parallel. |
* 'develop' of github.com:RocketChat/Rocket.Chat: (30 commits) [IMPROVE] [Apps-Engine] App user as the default notifier (#17050) [NEW] [Apps-Engine] New Livechat event handlers (#17033) [FIX] Change email verification label (#17450) Priority system messages were always created (#17479) Bump version to 3.3.0-develop Bump version to 3.2.0 Bump version to 3.1.2 [FIX] LDAP error when trying to add room with spaces in the name (#17453) Regression: Add missing cacheKey to mem (#17430) [FIX] Empty Incoming webhook script field (#17422) [FIX] LDAP Sync error (#17417) [FIX] Bot Agents not being able to get Omnichannel Inquiries (#17404) [FIX] Allowing blocking a user on channels (#17406) Regression: Fix mem usage with more than one argument (#17391) [FIX] Web Client memory leak caused by the Emoji library (#17320) [FIX] Omnichannel room info panel opening whenever a message is sent (#17348) [FIX] New user added by admin doesn't receive random password email (#17249) Bump version to 3.2.0-rc.2 [FIX] LDAP error when trying to add room with spaces in the name (#17453) Complement Guest role restrictions for Enterprise (#17393) ...
|
@zdumitru thanks for the feedback. We are evaluating adding a button to the header so users can decide on what behavior they prefer: expended or narrow. |
|
This pull request introduces 2 alerts and fixes 3 when merging 9367d01 into 6c2f4ff - view on LGTM.com new alerts:
fixed alerts:
|
|
This pull request fixes 3 alerts when merging 0ed366a into 6c2f4ff - view on LGTM.com fixed alerts:
|
|
Hey guys, can we make the checkbox "Also send to channel" checked by default? My users complain that they miss messages in threads because no message is send to the main channel. Using the "Reply in Thread" already ticks the checkbox, but clicking on a previous thread message in the main room does not. Or at least make it a configurable opton :) Thanks |
Same here. Thanks! |
|
A configurable option would be awesome. I think the default on false was correct. It would be furthermore good, to have a menu point on the lefthand side called See Slack screenshot: |
|
@ggazzo @sampaiodiego please take a look at the comments and offer a way to make de default-option configurable. This is really a pain for many of us how it is now.. Thanks! |
Try : My Account -> Preferences -> Messages -> Show thread messages in the main thread |
|
I have set this and works fine. It would still be nice to have a Thread Menu point on the left-hand side menu, where I get notified if there are replies on a thread where I'm involved. By clicking on it, on the main chat window, all threads I'm involved could appear and I could reply there or select one for reply. Imo the best way, you never loose overview. |
In my instance it is already enabled, but... To get it work in 3.5.0 I had to disable, save, enable and save again, worked as expected. I also made a comment here: #18347 (comment) |
He meant a Global option, not per user. Breaking changes to an established UI are not always popular - despite what designers may think - and frequently throw users, which then generates lots of ear bending, queries, and wasted time. As has been asked many times before, please leave the default as is, and allow admins and users to change if required. Changes like this often get missed on updates - this breaking change was only mentioned in this PR so even when reading bugs it means that it is missed and not read and understood by most admins. The first they know is they check the bug fixes, update, and the phone goes red hot. The release notes just say
No mention of breaking changes? Perhaps there should be a lot more detail in the release notes. |
Yes, sorry, I forgot to say that. I had to do in Administration -> Accounts -> Default User Preferences -> Show thread messages in the main thread If enabled, then disable and save. Enable and save again. I've updated my answer. Thank's. |
Nope. Tried that. On 3.5.4 I have tried to change the global default but it seems to make absolutely no difference to users so when they reply to a thread and their default is Off it appears to override the global default. So if I post a comment and the user replying has it set to Off then it sets the whole thread as off, so users then have to remember to tick the box (even me with User pref set on). Which they usually do not do - they don't even realise despite being told. Even though my setting is On I have to remember to then check the "Send to Channel" box myself. That can't be right can it? And as a result we have a lot of confused and angry users. Including me. How do we change every users default back to On? Anyone know the setting in the DB that I can manually change before I get stabbed? |
|
Hmmm. It gets set in: db.getCollection('users') No idea how to update them all to the new default quickly though. And no idea what happens by default to new users either? Going to be a long night doing it manually. Grrrrrrr. |
|
hey @reetp sorry for the delay, but I think you got (or I explained) it wrong... the personal setting and the checkbox are different things... the personal setting was designed to allow users to keep the old thread experience (keeping all the messages in the main thread)... the second one, is for the new design which omits the ordinary conversations from the main thread, and you choose if you want to send in the main channel if it's so important... actually we have plans to remove the personal setting and hide the ordinary messages from the main thread (its an option to give more time to users get used with the new style)... |

closes #17945
closes #16320
closes #17362
closes #15662
closes #16986
Since we are not displaying the threads on the main thread (only if you choose, but the message is not collapsed anymore), closes #17140
closes #16281
closes #17519
closes #17083
closes #16280
closes #14869
closes #14863
closes #16230
closes #16328
Before
After