Keep the messages in channels in chronological order
Whenever a reply is posted to a previous post, the post is moved to the bottom of the channel, thus moving it out of chronological order. This is much too confusing when looking through the channel to ensure each post has been responded to/answered. Please always keep the posts in chronological order. When clicking on a post notification/activity, this should take you to the post where it is located in chronological order, not at the bottom of the channel.
Tracee Bowles commented
Would also prefer the most recent be on top, not on bottom
Matt Olson commented
Agreed, it is very hard to keep track of the conversation due to replys moving messages out of order. Pls fix
Mathieu Cossette commented
We use conversation as GO for our deployement process and to keep logs for gouvernance and when activityes overlap, it's getting verry confusing. Please allow for an order selection by conversation.
Cameron Ackerman commented
Hi! I think this is actually a little confusing the way it's titled. It sounds like instead what we should have is a way to sort threads by CREATION time as opposed to latest update.
Right now it's very difficult to keep track of conversations because the threads keep jumping around as they're posted in. It would be nice to allow the threads to be sorted in creation order to circumvent this problem. Users would still be able to find updates to threads through the activity feed.
Doug Lee commented
Microsoft: I very strongly urge the addition of a means to make all chat entries in a channel appear in chronological order somehow. I am blind, so although the here-hated movement of a recently answered thread to end of list helps me find what changed, it is indeed confusing and does not scale at all to a channel with many simultaneous active conversations. "But chronological views don't scale either," you say... so here's one idea:
- Make a "Messages" List control of all chats, in chronological order (unthreaded). This gives me a MUCH needed way to read exactly all new material, just by arrowing down from the last-read entry.
- Add a new "Threads" List control containing an "All threads" entry and one entry per thread. As focus moves among items in the Messages list (e.g., via arrowing), highlight but do not select the corresponding thread's entry in the Threads list. If the user now focuses the Threads list such as with Shift+Tab, land focus on the highlighted entry. Make Selection via the Space bar, or a single mouse click, filter the Messages list to contain only this thread's entries.
Now, for a busy channel, I might move with arrows through the Threads list and press Space on a thread to read just its messages in the Messages list, thereby regaining current functionality. For slower channels though, I would always live in the Messages list and just read new additions as they arrive.
John D. Shkolnik commented
Microsoft didn't think this one through; they're trying to present a pretzel as a straight line. The main channel content should always be chronological messages, not threaded. It's the only way this sort of thing (IRC, Slack, Mattermost, etc.) stays usable. The threaded view would be available in a side panel like what Mattermost offers.
Ray Bishop commented
Has there been a switch or anything added to make chronological order work in Microsoft teams yet?
There totally should be an option to enforce chronology. The fact that any reply will relocate the original message in a thread is unbelievably confusing. Search, not sort does not apply here as a chat thread is chronological by nature.
benoit plouffe commented
and/or have a list of threads on the side that you can click and expand
Hugo Estrada commented
Keeping them chronological makes it easier for some of us to find previous conversations. Again, an option to switch them would be great.
Courtenay Hoffman commented
This is really important! If users type their responses on a new line (vs. in the "Reply" field), the replies become separated from the original comment. This is really bad. Furthermore, the "move" doesn't take place immediately - it happens when you leave the channel. When you return, the thread is moved. Terrible.
Lee I. commented
I want this too, but it could be provided as a setting option.