Mute a channel is still being worked upon. The team is still hard at work on this item. No updates at this time.
Muting a channel or chat (especially a recurring meeting chat) should have a timer attached to it.
If you know you are not going to attend a given # of occurrences of a meeting you should be able to mute it for the duration of time. To me this means that the controls are different for at least meetings compared to the general 1:1/group chats and channels--those could be general mute toggles.
Muting group chats that are highly active is a must, there are use cases for using group chat as opposed to creating a Team, where you can already do things like unfollowing but not being able to mute a group chat when you know the information being exchanged is not a priority.
Please advise on an ETA...
This request has been reviewed and declined by the feature team.
You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.
The problem with this feature is the O365 group that is created with the Team in addition to the subsequent SharePoint sites and other assets.
If creating a nested Team can be architected and acknowledged as something that will have all of it's files housed underneath the same parent O365 group and SharePoint folder/site structure this could be a great idea but very complex to execute based on existing Teams features.
Thank you all very much for the great response. The survey is now closed. The feature team will be reviewing all the data that was gathered and responded based on the findings.
Again, thank you for helping us make Microsoft Teams the best it can be.
Is there more information on this?
This request is still queued within our backlog. No new details yet.
Receiving a lot of questions about this from our coworkers, is there an ETA for this? Is it tied to the Skype convergence?
This is currently in internal testing rings at Microsoft, and the feature team is targeting a release to the public in early Q2.
~Alex & the Teams team
The biggest problem I've run into using Planner within Teams is that you notify the ENTIRE Team about comments made to tasks within the board. If you have different projects as different channels and only care about a given Channel it gets quite tiresome and spammy to continuously receive emails about other Planner board. This needs to get fixed to only notifying the users assigned to task and comment originator. This again is another use case for having different membership groups by Channel. If this can get connected to the Team and you receive a notification in your "Activity" tab while also receiving the email notice.
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 currently working on defining a compact mode experience. I will post more details when we have more to share.
This item is still queued up in the backlog. No additional details are available at this moment.
Really keen on this feature, use case after use case for templates keep coming up on a nearly weekly basis.
Can you provide an update for this?
This feature request is still being worked upon. No additional status to share
Items still in the works:
2), 4), 5) and 7)
Items we cannot repro:
6) and it doesn’t appear people are hitting it, but let me know
Items that are completed and in the public release:
1) and 3)
I believe I've seen other similar tickets for this on here but yes, having the ability to know that the notification is from a file being edited or a meeting being created versus a simply chat message would make it more of a priority to get to.
We definitely need a variety of options beyond the @team @user and follow/unfollow. Perhaps most importantly, receiving push notifications comparable to what Skype offers would go a long way to driving engagement and keep our organization aware of activity in their various Teams....
This is a known issue — will update you when I have more info.
This request has been declined by the feature team.
Private channels may help with items such as this request once they are released. The Private channel topic is tracked at http://microsoftteams.uservoice.com/forums/555103/suggestions/16911079
Please note the handling of “Guest Accounts” is a separate ask and can be found at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16911109-guest-access
The request about “Guest Access at the Channel” level is being tracked by this request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577-guest-access-should-be-implemented-at-the-channel
Thank you all for the feedback.
This is a must. There a growing number of problems associated with not being able to change membership by Channel within a Team. One use case I just detailed on a Planner related item is as follows....
Using Planner within Teams you notify the ENTIRE Team about comments made to tasks within the board. If you have different projects as different channels and only care about a given Channel it gets quite tiresome and spammy to continuously receive emails about other Planner board. This needs to get fixed to only notifying the users assigned to task and comment originator. This again is another use case for having different membership groups by Channel.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
The biggest problem I've run into using Planner within Teams is that you notify the ENTIRE Team about comments made to tasks within the board. If you have different projects as different channels and only care about a given Channel it gets quite tiresome and spammy to continuously receive emails about other Planner board. This needs to get fixed to only notifying the users assigned to task and comment originator. This again is another use case for having different membership groups by Channel.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
113 votes31 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →
Work is in progress for captioning of meetings. Captions for calls will be worked on after meetings is released. We’ll keep you posted.
This is a definite must for our organization as we serve students with hearing disabilities and will require this immediately
The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.
Understandable that MS would be hesitant to drive users away from such a high profile product as Outlook but there are multiple use cases for having an integrated Outlook / 3rd party email tab such as these two....
1. Remote workers that really on OWA and Teams webapp OR desktop, it would be great to deprecate their need for OWA and allow them to access email from the Teams web app
2. The desktop use case is just as strong since the Teams meetings syncs with outlook as it already syncs with your outlook calendar so it would be great to access your emails from the same tool.
Teams has a strong opportunity to truly become the hub of Office 365 and leaving out key products like Outlook while integrating with Planner and other productivity oriented tools would be a severe misstep....
This is a feature that would significantly improve adoption of Teams and overall productivity in our organization. We've been implementing a unified communication system focused on Office 365 and if one or more of the tools can drive all tasks or collaborations in this manner it would be massively beneficial.
We are still considering this feature for future releases, and will continue to update the status when it changes.
Is there an update that can be provided on this feature? The active power users are fine with searching for historical information but seem to be annoyed with the ever growing list of chats just as much as the typically resistant users...