08-11-2017 11:44 AM
08-11-2017 11:44 AM
Heya Microsoft Teams Community,
Is there any word on Devs giving us the option to disable threaded conversations in the General Teams Room? My team currently uses Hipchat and we chat in pretty high volumes. Having the option to disable threaded conversations would let MS teams work for us. Currently because of our high chat volume and multiple conversations we cant use teams because it can't keep up with the threads. If someone is responding to a thread and a few new ones get started or their thread gets bumped up it removes what they were typing and they lose track of the thread.
Thanks for the feedback
08-11-2017 02:43 PMSolution
Cheers @Juan Carlos González Martín :)
No option exists currently, and they've declined to take on features like this in the past: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16941412-remove-threads-featur...
An option/switch is maybe more friendly to them compared to pure disable, but it does move in a different direction than where they seem to be headed now. Personally I would never disable threading, and simply train my users to use it universally. Once people understand how it works and why it is valuable to use it, we've seen far more success than previous unthreaded chat solutions.
The only places I've seen unthreaded chat work well is a team that has the culture of hanging out in that chat together during their entire work day. For our org, this is not really possible as people have in-person client meetings etc that take them away from watching that chat constantly. This results in them being left out, and they either have to scroll way back and try to piece things together or they give up and abandon the tool completely in frustration. Once people start to abandon the whole thing starts to unravel somewhat. Threading lets them quickly see the subject of each conversation and skip the ones that don't matter to them.
08-11-2017 03:24 PM
Thanks for the reply. I agree having the option to switch this feature on/off per room would be a great option instead of outright disabling it. For our smaller groups of the threaded view works great and is easy to track conversations.
Our main issue was using this as our main communication piece for the team. We have 50+ people on at one time in a call center environment. We're constantly asking new questions and trying to reach out to different experts to resolve issues.
Our test runs moving to Teams from Hipchat have been rough so far. Trying to use Teams to chat with this many people gets hectic very quickly. Our biggest roadblock being the threaded conversation view. Without the ability to turn off threading/change the scale of text we're running out of screen room and our conversations are being cut short.
As you can see by the screenshot included we got about half way through a sentance before another conversation was bumped down to the bottom. When this happens it stops text from being entered and started typing in the new conversation window. It got to the point where there were multiple 50-100 reply conversations trying to fight over the space at the bottom of your screen.
08-11-2017 04:09 PM
Definitely understandable, and that new thread pulling you down mid text entry is definitely a bug. If you haven't already, please report that in. I think your screenshot captures the issue quite well.
08-13-2017 01:02 PM
08-14-2017 03:38 PM
Yeah What Steven said.... sounds like you guys need to make use of channels.
One use case for unthreading we do is work streams. On server update days with my team we just pop to a group chat, add everyone and start chatting. This is basically the same thing as unthreading a discussion since we prefer it over threaded. We would have liked to have had a channel that's not threaded for this, but the work around works fine. You can even name the chat like a channel. However, if there is no activity after like 30 days or so, the chat goes away, just keep that in mind.
08-14-2017 03:46 PM
It doesn't actually go away, it is just falling off your recent list because of the inactivity. If you create a new chat with the same exact people again, you'll see all the history pop right back in.
Currently all chat messages sent from users in Teams are kept forever. Additional features are coming later where admins will be able to set and control this retention period etc.
08-14-2017 03:51 PM
I thought the same thing but I'm pretty sure we used the same people in our chat and there was no history. I know you can Compliance search the stuff due to journaling but was curous about hte history thing. I've even scrolled back with 1 to 1 chats and noticed they only go back 30 days in client. So there is definatley something there not rendering or returning chats back after so long in the client.
08-15-2017 09:54 AM
I'm definitely seeing chat history much further back than 30 days in my tenant. Sometimes it has to spin a bit and load it when I scroll back up, but it always come through. I just came across one all the way back to August 1st 2016.
Your org isn't doing something like purging Exchange data or anything like that are they? All of this uses the Exchange backend, so that could be something to examine.
If not, you may have some sort of issue or bug going on. Would be good to report that in so the team can have a look.
08-15-2017 09:56 AM
yeah, i know it uses exachange is why I was confused, but aparently it must be the chat I looked at didn't have the exact same individuals in it. I found a few people going back to May so think we're good.
08-21-2018 09:04 AM
While I respect the "just teach my users to..." comment, that flies in the face of all things UX/UI design. Things should be intuitive and shouldn't require teaching. Especially something so core to internet communication as chat. The reason Slack and Hipchat have done so well comes down to linear conversations. That comes all the way back from early internet days with Internet Relay Chat (IRC) and the windows chat client mIRC. We're talking early 90s internet. They had channels. Everything was linear. It worked and it worked _really really_ well.
I get that Microsoft is trying to innovate but ultimately threading is an antithesis to everything internet chat has been to date.
08-21-2018 11:08 AM
09-08-2018 07:04 AM
It should be noted that threaded conversations are in the Team messages, but aren't used in chat. If you create a named group chat the experience is pretty similar to other platforms.
07-29-2019 10:36 AM
07-29-2019 10:44 AM
@Chris Webb Apologies for not being clear.
We *LOVE* threaded conversations and can't imagine going without them.
I'm specifically referring to the issue where, while replying to a conversation, if a new conversation is posted or a reply is added to a different conversation, focus is lost on your reply and the channel window scrolls up to the latest conversation. This causes you to lose your place in the reply and have to scroll back up and click back on the conversation to continue typing.
07-29-2019 10:46 AM
07-29-2019 11:28 AM