This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
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.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
I rarely use Teams, but occasionally someone mentions me in a channel so I get and email, which forces me to open the platform. Then I tend to reply by starting a new conversation, then I realise my mistake which enrages me and I give up on it once again.
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.
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.
Hey guys, thanks for the feedback – we hear you loud and clear. After talking this over with the Engineering team, I confirmed this will remain on the backlog and we are actively considering how to accelerate.
Tweet me if you have any questions! @skprufo
Just to reiterate, without this feature we can not use Teams as it's useless since many people in our "teams" that might otherwise be able to use Teams have Linux desktops. As such, most people are using Discord.
Please don't abandon this. Teams wont be a viable alternative to the other similar products that provide rich Linux clients until you sort something out here. How about just permitting it to work in Chrome and utilise the Notification API?