Additionally, when I do receive an email due to a Planner Task comment, it's not obvious that this was generated from the comment. I was looking for the message in the Conversations tab, and it took me a while to realized it was a task comment.
If we can't adjust how these task notifications occur, at least make it obvious that the email is generated by a task.
Yes, emailing everyone assigned to a team when a Task comment is made has become a real pain point in one of my ~55 member teams. The Planner integration is awesome, and is improving, but this notification problem generates the largest volume of negative feedback I receive. For example: "Unsubscribe!" "Please remove me from this team" "Please stop with the task comments!"
Reiterating the desire to allow restriction of comment notifications on task cards to only those assigned to the task or involved in the comment thread. We have ~20 people working through several distinct work streams, and everyone complains when someone comments on a task and it's broadcast to the entire team. Please work this out!!
Related to this, when I attempt to switch from one team to another, I usually find myself clicking on the team name in the channel hierarchy itself rather than one of the channels. This click only collapses the team. I then need to click the team name again to expand the channel list, then click the desired channel. This becomes incredibly frustrating after a while.
A potential solution would be to only allow expand/collapse when clicking on the triangle to the left of the team name in the hierarchy.
Additionally, I would expect a click on the team name in the hierarchy to take me to the same location as a click on the team name in the breadcrumb at the top of the workspace (where you can access the Members, Channels, Settings, Apps tabs)
Thanks for your consideration!
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.
There may be existing solutions to several of these situations, but for what it's worth, here is a use case that has been growing in our organization:
Various "working teams" come together to address various projects, questions, etc. Each working team also has a separate small Steering Committee to provide guidance and approvals. When we first started using Teams, we would add all of the working team and the steering committee to the respective Team. However, the Steering Committee didn't need all of the @Team level announcement/comments, especially since they are often on several different Steering Committees at once. As a result, we began setting up separate Working Team and Steering Committee Teams for each project.
We would love to set up a Steering Committee Channel within the Team to ease administration of a given project, facilitate easy communication with the Committee, yet also restrict @Team mentions to Owners/Members of the Working Team itself (or perhaps direct @mentions to Owners/Members/Guests directly).
For a given Steering Committee member who is involved in several committees, it would also be great to group those respective channels in the side bar to keep things clean.
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.
This item is still under review. I’ll keep following up with the feature team and sharing all your feedback.
Another thought here is that we've often begun a number of conversations in the general channel, then later created additional channels. There are often conversations still occurring in the general channel that should be moved to the new one.