We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Internal education attempts aren't working. Users continue to fail to grok that "chat is like Instagram and channels are like facebook". Anything you're probably iterating on must be better than the current UX. How about we compromise for now and you pick a rando solution and implement it now. Later, when you arrive at your favorite solution, you can then implement that. Personally, I don't think the current feature is hard to understand, but since Teams forces me to collaborate with humans, this problem won't go away. :-) I appreciate whatever you can do to speed this up.
This feature remains on the backlog. We will update you when we have status changes to share.
143 votes16 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
Thank you for your feedback. Many customers have asked for reporting capabilities around Praise, so this will be one of our top items in the list of things we want to add to Praise in the future.
87 votes9 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
Thanks for the feedback! Custom Praise (both images and text) is our top ask from customers and we’re prioritizing this highly for future feature development.
This feature request is working its way through the backlog queue. No new details are available yet.
Screen sharing on Chrome and Chromium-based Edge is now supported. We also have released support for joining meetings from Safari, Firefox and IE browsers, with some limitations. For details, please see the following link: https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams#browsers
I'd like this feature added back. (As I recall Teams used to have a way to to determine this. You could "manage the Team" and see how many people were following each channel. Then you could click the number and see the list of followers.) When added back, it would be preferable to be able to view it within the channel itself somehow.
My real-life use case is there are a lot of people in the team, and an email thread going around. Now I have to reply to the email thread with a link to the channel post because I have no idea how many of those people are following the channel. If I could see the list, it could save me (and everyone receiving it) an email and at worst I could mention those not following. Great product Microsoft. Keep making it better!
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
This request is still queued within our backlog. No new details yet.
You can integrate Microsoft Planner or Trello as a tab in any channel in Teams. Just click the little + sign in your channel’s tabs section, and choose Planner or Trello from the pop-up window.
I agree with Marco and Theresa and I think Suphatra may misunderstand the original request. An individual could create a private one-person team in Teams and then use that to maintain one or more personal planner boards but that seems like a lot of overhead.
Teams for managing personal work has not yet reached feature parity with the web version of Planner. Within Teams, on the My Work tab under Planner, one can not yet add a Planner board. One must add it in the web-based Planner first. Because there are workarounds (i.e. using Planner website, creating a one-person private team), this is not among my higher priorities for new Teams features, but I am voting for Teams (and the mobile app) to reach feature parity with Planner at some point. Keep building Microsoft. I look forward to more features!
This feature is now on the backlog. I will update you when we have more details to share.
Thanks for the update Warren.
I wish it was in an active development sprint, but I appreciate the update on where it stands at this time, Warren. Looking forward to whatever you've prioritized higher.
I was just in a meeting in which I proposed the use of Teams to solve some painful communication problems. We looked at the Wiki for important information that needs to persist--SharePoint, while a fantastic product, requires too much overhead for our current capabilities. I had trouble making the case to the emperor of our company who recognized the deficiency of not being able to search the Wiki. Help me Obi-wan!