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.
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
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. We will keep you posted as we have new info from the feature team.
We acknowledge the customer demand for Private Channels and have been hard at work on it. Private Channels is currently in preview with a select group of customers. We expect to release the feature to the public later this Fall, and will update here when we are starting to roll out to all customers. We appreciate all the feedback you have provided to us on this forum and thank you for your patience.
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.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.