Threads should be breakoff conversations like Slack. The current way threads are handled are horrendous to manage. Still notify on thread replies but they should stay where the thread started in the context of the conversation.
David Gee commented
could not agree more - there are no threads i conversations - makes teams almost unusable. Slack has this nailed and we would switch to it in a heartbeat - teams is so limited, has no bots, poor external application integrations - i could go on and on. MSFT is 3 years behind here....
Brian Handscomb commented
Own personal opinion is the Teams thread function is less than helpful - Teams seems to randomly "collapse" threads, re-order them in Teams tab (which works differently to Chat tab like it's a different application), and give obstacles to use (reply links and new conversation button).
IMHO much better would be for Teams tab to work like Chat, a stream of messages with a simple compact entry box at the bottom, but still provide ability to reply to message (like current Teams thread functionality), and I think similarly to Slack a message with a reply thread should just have a link/button to pull up and/or add replies in a breakout side panel. The side panel idea would allow a user to reference some other message for information to use in a reply. This would allow for a more compact and IMHO refined layout.
Furthermore I would suggest at no point should the Teams message listing be re-ordered because of a new thread reply. Moving a thread because it has a new reply to draw attention to it (because the notification system leaves a lot to be desired) messes with a persons "mental memory map" of where messages are in relation to each other.
Timothy Carroll commented
I don't understand how this doesn't have 10,000+ upvotes. Threaded conversations are dead simple and intuitive in Slack. The way Teams handles conversations is simply unintuitive, difficult to explain, and hard to keep up with.