Better visual delineation between `Reply` and `Start a new conversation`
It's very confusing to new users that there is a difference between replying to an existing conversation and starting a new one within a channel. This is a visual thing as much as anything else. The 'reply' buttons are not naturally attractive if you just want to start typing a message. There should be a logical gap between the bottom of a conversation and 'start a new conversation'. 'Start a new conversation' needs to be separated visually, as if it's a second order command rather than a first order...reply.
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.
As if teams did not yet require enough clicks for all kind of actions, now I also have to click a button before starting a message in a channel? You have to be kidding me...
Not saying this feature makes the view worse, but could you at least give a choice what to use per user? If the people are OK with the New Conversation button - fine, but it should be revertible for a simple view without extra buttons.
Hallo, I saw today the "New conversation" button in MS Teams.
I don't understand why you created this button, since a few people are not able to use Teams correct.
Now 99% of users who know how to use the Application have to click an aditional button in Teams to start a conversation.
I don't know from the usability perspective if this is the correct way, since I have now to navigate with the mouse to this small button to click it to start writing. :(
Please invest in the availability to disable this button by settings.
Great work on releasing the "New conversation" button but..... can we have it that the button opens up with "format" expanded mode by default and the cursor waiting for typing in the "Add a subject" field?
Not having a subject at the start of a New conversation is like an email without a subject....making it even harder to find it later.
If the "New conversation" button opened up with the formatting look, all the options are available after ONE click. Post in multiple channels, Announcement, Subject.....
So the "New conversation" button is "ahlf way there" to being really effective.
Available now in my targeteted release tenant.
"September 11, 2020
Push the big button
Introducing the updated New conversation button in channels. Confidently know you're starting a new conversation (and not replying to a thread) with the new button look. The same old keyboard shortcuts will still work for you and you can find those in Keyboard shortcuts for Microsoft Teams.
The new button is at the bottom of the channel. Select, New conversation to open the box where you write your message. Just as before, you can type a quick message and press Enter to send, or select Format Expand button to expand the box and use your formatting tools. Select Send Send icon to send your message when in the expanded mode. "
Gabriel Nelli commented
YAY!!! We are seeing this now and I am doing my happy dance! :)
Jim Tuttle commented
The update is available for some clients, not sure how they determine who gets it, but yes, it's out, and it's great. Finally!
Oh wait, it's available now!?
Adrienne Haywood commented
Speaking as someone who's (many times) had to delete the new conversation I accidentally just created and paste it into the reply that was intended... I love this update. Fantastic, thank you!
Dan Muller commented
I've been using a version with this change for a couple of days, and really like the way it was done. Should cut way down on conversation spamming by Teams newcomers.
It looks like some users have a new version:
Marco Dileo commented
Did the test went well?
Now it’s definitely time to release this.
Dan M commented
It looks like this is starting to be released to targeted release. I didn't see a notification about this in the M365 admin center though. Might want to get that posted since I now have the "New Conversation" button at the bottom of the channel Posts
Derek Harper commented
Place the "New Conversation" field at the top of the pane. Simple solution!
Very much needed!!!
Dan Smith commented
In addition, could you have an administrative-level option to "always display the full editor pane" when starting a new thread?
We'd like to make sure that users add a "Subject" to their threads whenever they start a new one.
Right now, they need to click on the "Format" button before they can see the "Subject" field.
As a side note, I (Teams Admin) provide mandatory training to all new teams owners. There is only 4 things, one of those things is to watch out for out of thread replies. That how serious this is.
This wouldn't be a big deal if you gave us (teams owners) the ability to move a new thread under an existing. It would use date stamp to sort in the thread. This works both ways. It would be great to be able to rip a reply out of a thread and make it its own for times that a side conversation hits critical mass. Please consider. As an owner I dont mind tending to the rock garden that is my team, but I need the tools to do so.
This is remedial. We work in a fast paced environment and it takes to long to click new conversation when needing to respond to a firecall. There has to be a certain level of responsibility with the end user. It's not that difficult to figure out the difference between a thread and a new conversation. We have been using this in our work environment for over a year and a half and have seen little to no complaints. Microsoft's efforts should be better focused somewhere else.
On behalf of myself and my coworkers. Please stop testing this new conversation button. It has popped up by mistake on at least 3-4 updates and we hate it. All 20 of us.
cant be that hard. Just leave the regular reply field open under EVERY threaded conversation and make new conversation a simple button to open the input field. Voila: no effing annoying accidential new conversations any more.
sorry if this has been posted by someone in the past already, but I did not read 768 comments for a simple fix, that should have been done years ago.