This item is still under review by the feature team. I have no details as to when a decision might happen.
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
We’re updating our command library all the time, so keep checking the menu in the command box to see what’s new by typing / or @.
Thank you for your feedback. The feature team is currently working on introducing pinning to posts and replies in channels. We will share an update as soon as one is available.
We have added a lot of new settings changes since the last update. You can see the updated list here https://support.microsoft.com/office/team-owner-member-and-guest-capabilities-in-teams-d03fdf5b-1a6e-48e4-8e07-b13e1350ec7b.
We would like your feedback on any gaps or additional settings that you feel are missing. Please let us know, the team would love to hear from you!
We are happy to announce that the New Conversation Button has started to roll to the general public, and should be rolled out 100% over the next week or so. We will share another update as soon as one is available.
An error occurred while saving the commentMichael Rayman commented
I second the request for wireframes of what the UI would look like to separate the reply from a new conversation. On this separation, this is a difficult UX challenge to solve. Slack and other tools simply don't have to solve this problem because they don't support threaded conversations within a single channel.
I can see how having this feature could be beneficial, but even the problem it tries to solve eventually surfaces again when you have so many different threaded conversations in the same channel's history, you have to hunt in the channel history to find the conversation you want to reply to or read updates from. It simply makes more sense to see the most recent messages always at the bottom of the chat history so it's a totally flat list of messages organized in time. There may be no way to make everyone happy unless you provide an option by which some can disable threaded conversations on a per-channel basis. I would imagine this would be rather easy as direct message chats don't have this threaded feature.
Finally, let me just say that the way Teams is currently implemented where your focused text field is always ready to make a new conversation is just so unnatural. Instead, the vast majority of users expect the default text field that has focus after each press of ENTER is to make a reply to the last conversation not start a new one, especially when people are chatting back and forth real time.
I feel the default behavior should be this:
* DEFAULT: type a message, press ENTER, type another message, press ENTER. these all are in the SAME conversation
* Explicit Action: there should be an explicit action to make a NEW conversation so that this is not the default
Right now, it's the opposite.