Anonymous

My feedback

  1. 9,460 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1159 comments  ·  Public » Wiki  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    So far I have learned that the Teams Wiki feature is not searchable, not exportable, not easily copy-pasted, not persistent (is removed when tab is deleted), cannot be moved between team channels, and cannot even last-ditch-effort have its Copy URL option be used to create a new tab without strange results within the Teams desktop app.

    Any single one of these would be a barrier to adoption. But all of them? That's a Fail.

    To add insult to injury trying to use OneNote, instead, inside the Teams desktop app, presents the lovely experience of constantly having the section / page / subpage lists disappear as soon as you click to edit any content -- requiring a selection of Open in Browser, or Open in Desktop in order see the content hierarchy while editing a portion of said content, and completely breaking from the unified experience of using teams. So another Fail.

    (This, all on top of the fact that they claim to know better than us what channel content is of primary importance for that channel -- and it's obviously Chat and not Wiki or anything else of.... primary importance to the actual users. Fail #3.)

Feedback and Knowledge Base