Do NOT reorder messages based on replies
If a message has replies, Teams changes the order of messages so that the original message takes on the timestamp of the latest reply.
DO. NOT. DO. THAT.
It is horribly flow-breaking to have the original conversation reordered based on later replies. This is totally unnecessary. The Activity feed can help me quickly jump to "new" posts regardless of their location in the channel order.
Don Shrout commented
This would be a great per channel setting to have. In most channels it makes sense to reorder the threads based on replies. It keeps the active conversations near the bottom of the list.
However, we have one channel that, every time a developer submits a Pull Request, a message gets sent to a specific channel to notify other devs so they can review the PR. We use that thread to notify the original developer when the PR has been approved (or not approved).
Sometimes a PR can get "lost" because of the conversation on other PR threads. The unread PR thread gets pushed upward and off screen.
I would like to be able to turn off thread reordering for this one channel.
I've attached an image that shows how a PR thread can quickly get lost, even with replies collapsed.
This is particularly irritating from an internal communications point of view. Really important messages get lost for hundreds of people because one person has a query/makes a comment on a post from a week ago.
Give me an option to disable this. Messages need to be chronological!
One of the main reasons why we can't moved completely off of Slack. Its way too frustrating for the main thread to be railroaded by a sub thread so the main thread is unreadable
It's more like a bug that they're calling a feature without being smart enough to fix it. Fire whoever came up with this,
Just link replies to the original post in a thread (send notifications re additions to threads but that is all)
. Do NOT re-order. Agree, posts are being missed.
A total turn off. Please fix this. Important messages are being missed.
Ashley Snowdon commented
Yup, very very very annoying!
Guy Elsmore-Paddock commented
I lose track of messages *so often* because of this. I am often looking for a particular conversation, but as I scroll back I see a message I thought was longer ago and stop scrolling. Then, later, I realize the message I am looking for is now even further back than I realized because an older thread moved forward after someone replied to it.
Hadi Albalkhi commented
I totally agree with "Do NOT reorder messages based on replies". Please do it this way!
@Ryan imho this is not true. It doesn't make it easier to find things, since messages and threads get reordered all the time! You lose your visual and chronological anchors. One usually would search according to: "ah it was before this problem happend, before this and that post or it was last week when we first started talking about this issue" and so on. A fixed timeline (according to the timestamp of the first message in a thread) ist much more helpful to search through manually.
Charles Dong commented
I completely agree!!! This feature is sooooo annoying!!!
We use threads on a daily basis, it's important to reduce the clutter. When Teams reorders messages based on replies, plenty of questions and important information gets lost, which makes people use threads less and have discussions less
Teams should not reorder messages imo. Its very confusing and causes older posts to be lost.
This is driving us crazy. Please can you copy slack's behaviour
Please please please stop doing this!!! It's soooo confusing and is horrible
This is the most confounding design flaw I've found yet in Teams - and there are a lot of stupid design decisions that have been made up to this point.
Some people may like this reordering feature, but personally it is highly confusing to have the item you are reading move while you are reading it. Seems like a good solution would be to let people who don't like it turn it off
The ability to turn this off would be extremely useful
When using threads to reply this can cause new messages to get lost if an older thread is more active.