Add option to have non-threaded channels
I'd like the capability when I add a new channel to make it non-threaded. Threaded conversations are great for some channel topics, but other more casual channels get too cluttered with multiple threads. I'd prefer to have the flexibility to decide which format I want when I create the channel.
This request is still being considered by the feature team but a final decision has not yet been made. I’m still awaiting more details.
The conversations in channels are not particularly space efficient either - the threaded, yammer-esque view doesn't make use of much horizontal space, and doesn't encourage chats / team discussions. I love the general design and if the team channels were more like slack I think more of my team would be keen to use the software!
While threading idea itself is good current implementation is not. Especially when split happens - one set of ppl write in 1 thread, and other writes in another thread and even worse when more than 2 of such splits happening.
Outer chat where threads jumping one before another becomes super annoying and confusing!
Some people got confused and write not in a thread but in "root" and it's becoming complete mess.
Maybe add tabs/side-panels to fork threads.
In case of small threads (2-3 replies) it's ok to have it in common chat, but there should be possibility to "fork" it from the main chat to some more persistent and visible place.
Robert Wiesner commented
I would also be happy to have a preference for Threads.
I currently don't like it, when an old threads is pushed to the top, if somebody replies to an old thread.
Allow the user to keep the "Message Order", this means responses to Threads don't move the Thread to the top.
R Cheld commented
They have it backwards. Chat should be the main interface with unlimited users, not 10 max. The threaded chat should be the sub communication tab for announcements and topic discussions like a Yammer interaction. Have the ability to reply to a chat post and automatically make that a threaded post in the other Yammer like tab or mimic what Slack does with post feature. Hopefully they read this and flip it correctly!
Please, this is a major issue for our less technical users!
[Deleted User] commented
Being a rival for 'Slack', the current chat layout is rather confusing. By default, you're more likely to start a new "conversation" than reply to the ongoing one. The current Yammer-like experience is not so good and brings confusion. Hence it would be good to clear the difference between these two and to improve the chat experience, the current Reply-rows are taking up way too much space.
Marcin Niczyporuk commented
I definitely would like to have "threads" in chat rooms. Chat rooms are not only for real time conversation. Sometime you have to leave the conversation for few hours, and later when you are back to the room, you could continue some unfinished talks in threads, which is awesome.
Marcin Niczyporuk commented
Actually threads are very useful, as they organize the chat. Having possibility to comment specific message and thus forging it as a thread keeps the chat clean. In skype it's missing and therefore people very often do "copy & paste" specific messages as quotes to, which they're providing answer. it's time consuming and polluting the chat, especially group chat.
Joshua Go commented
100% agreed. Very difficult to find new messages. I like a simple straight up single threaded chatroom. I.e. hipchat. So clean and simple.
Ben M commented
Agreed this conflation of Threaded Messaging and Chat leaves us with the worst of both worlds. It's trying to stretch it to far. You have a chat room, and then within that room, you have MULTIPLE separate Chats happening, on different threads, and it's very. very. confusing.
There are definitely places where threaded messaging makse sense, but not as part of a REAL-TIME chat
Tom Gibson commented
Threaded messaging is great in the right context - its generally very useful to contain conversations within a topic. Sometimes however its good to create a 'banter' or general chit-chat channel, and these sorts of channels don't benefit from the feature.
Shane Day commented
Timeline is my preference - maybe a "in response to" in order to look at a "thread" if you need to see the history of a particular conversation is good. Yammer suffers horribly from "threads" - don't repeat it here!
Kevin Hartman commented
Threads in the conversation make it too difficult to notice new messages. Let's keep this simple and have conversation history ordered chronologically. If users want to make a "post" and have a discussion on that post, this isn't the right forum. They should use Yammer.
Current Teams style is Reply will merge into Thread. This is very nice for single thread to chase discussion, conversion and bring synchronous experience.
In other hand, Slack and similar tools are line up message by Timeline. This brings better asynchronous communication experience.
Both is nice and it will be very happy if Teams allow users to select which style is prefer. I feel thread style message line up will keep user's conversion timeline but breaks conversion itself time base sorting. For instance, if user reply to 30day ago conversion, than that conversion will bring to top and I feel it's too noisy, just quotation is fine enough.
How about you?