Sam Hall
My feedback
-
9,711 votes
Unfortunately because of changing priorities, this feature was moved to the backlog. The team hopes to pick it up again in the near future.
Sam Hall
supported this idea
·
-
20,077 votes
Thank you for all your responses to the design survey. The survey is now closed.
Sam Hall
supported this idea
·
-
3,285 votes
The team has not made a decision on whether to move forward with this feature. We will update when we have new status to share.
An error occurred while saving the comment -
62 votes
An error occurred while saving the comment Sam Hall
commented
Microsoft shouldn't try to shoehorn a **** Wiki feature into Teams. Just provide the integration hooks for decent wiki platforms and be done with it. How much time and effort will the Microsoft Teams dev team have to waste on this feature which is fundamentally flawed? At least change the name to avoid confusion. It's more like a place where people post content that other platforms would consider "Sticky Posts" or at best it's a "Channel Notes" feature. A Wiki it is not.
-
88 votes
An error occurred while saving the comment Sam Hall
commented
I agree, this "Wiki" feature is useless bloat. I found the feature amusing at best, especially the way you can actually have multiple Wiki's in a single channel (just to confuse it's purpose even further). Fragmented knowledge, hidden and scattered across channels really flies in the face of what a "Wiki" is about.
When I look around our Teams channels, the wiki feature's usage is limited to what I'd call sticky posts on other platforms.
Sam Hall
supported this idea
·
-
19,192 votes
Thank you for your votes and comments on this feature. The team is in the process of finalizing designs for deleting private chat threads. I will update as we have more progress to share.
Sam Hall
supported this idea
·
As a team leader, this is a terrible idea (I'd have thought that the reasons are obvious, I mean the clue is in the name of the product). A successful team collaboration tool should offer private IM features as an exception to the normal channels of communication. Blurring the distinction between the two features is not conducive to open and collaborative discourse. I would have to abandon using Teams as a team collaboration tool if this were implemented and I'd suggest you rename it to something less misleading if you did implement this.