Lock thread reply position
When someone sends a message as a thread, the thread needs to stay where it is.
When another user speaks, it's counted as a thread.
If you have 2 threads, and someone replies underneath the older thread, it becomes the newest thread on the list.
This causes me to miss entire chat histories, and re-read the same thread multiple times.
I want an option to lock the order of chat history, I don't care if it's a thread or a reply.
Even better, get rid of automatic threads entirely. Let everyone just send a message in teams the way you send a message in "Chat" - Let people create threads as an opt-in, rather than an opt-out from every single message in a chat.
The chat history gets all mixed up by this terrible concept.
I would really like to chime in on this.
Trying to make a Advent Calendar on a Teams channel this year - and it doesn't work really well with the different dates keep popping up and down, depending on which one people are commenting on.
There should absolutely be an option to lock the conversations, so they appear in chronological order.
This is the biggest issue I have with teams. Chat history is chat history. Regardless of "thread" or "reply" It should be able to be locked in chronological order of thread, and new replies should not have the ability to move parent threads. Let threads control the order on the page.
Also, maybe add a side window, or pop out window to show replies within specific threads.
Slack does this correctly. Honestly one of the best parts that differentiates Slack from Teams.
The way Teams handles recent comments and moving threads is driving me insane.
Paul Welp commented
I can see this being something that organizations (or even individuals) would like to be able to control for themselves. If this can be a setting at some level, it would give everyone what they are looking for.
Jerreck McWilliams commented
100% this. Re-ordering threads is a usability nightmare. Take a lesson from slack on this one - keep the threads in the same place within a conversation and maybe add something like an All Threads channel that's pinned to the top of a Team.
We recently switched to Teams from Slack and this was the #1 pain point for our teams. It was way too difficult to follow multiple in-depth conversations.