This feature request is working its way through the backlog queue. No new details are available yet.
Suphatra - this is not what the what idea described .... - Looks like you completely misunderstanding what people need or you never created a Team in your own application.
Creating new team is going to generate new site collection - named by the name of your team - this is the way you have to create teams by your design. Idea / ticket was to give ability to create team from already existing site (believe or not, people could have some sites already in place before you created Teams :) ).
Then, when you have your team and new site created, Teams are generating subfolders connected with channels - lets say you create Channel "Developers", people are using it, and then you figure out you need to change the name to better reflect a cause - this would be "Dev - Web" - but you want to keep history of it so you don't want new channel. So now you have a channel named "Dev-web" connected with a folder "Developers". We want to change this relation - we want to change those default assignments - not libraries itself because channels are pointing to folders not libraries.
This is I guess very obvious for so many users, it looks like you don't understand the way users work with Teams unfortunately :(
Please change status of this Idea as it is not even close to the solution.
The feature is still being worked upon. Many different changes are going into Teams and will provide a slow but steady pace to our performance increases.
I don’t have any new details at the moment but hope to get some additional feedback in the next several weeks.
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”
This feature item is still in the works. Unfortunately I don’t have any additional details to share. I will keep you posted as I hear new info from the feature team.
Hi Everyone – thank you for your patience. As was commented by someone below, Suphatra is no longer at Microsoft, but rest assured we are working on this feature.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
This is in internal testing. I don’t have exact timing for you, but wanted to let you know it is coming!
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.
This item is still under review by the feature team. I have no details as to when a decision might happen.
This suggestion is still planned. I don’t have further updates on timing, but will share as we have them. Thanks.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.