Mads Nissen

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen shared this idea  · 
  2. 121 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen supported this idea  · 
  3. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen supported this idea  · 
  4. 11,423 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1316 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen commented  · 

    The ability for an owner to do "Move Channel" or "Copy channel" would be *incredibly powerful* in a content management perspective. The biggest enemy of Teams adoption is duplication of content, and the defocusing of conversation. Move or Copy channel should provide the option of including chat history, Files and tabs in the transition to a different team. A limitation on visibility (aka only public-public moves) would be ok. An option for "auto invite missing members" would make sense but is not an absolute.

    Leaving behind a forward link both in source document library and source team which directs users to the new location of the channel would be magnificent.

  5. 48 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen supported this idea  · 
    Mads Nissen commented  · 

    Also the conversation in the channel should show the time-posted label with a hover that displays what local time it was posted in. Furthermore, the Appointment scheduler should show options for the participants (most likely) timezone.

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

    We’ll send you updates on this idea

    121 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This request is now being reviewed by the feature team! I’ll keep you posted as to the future decision.

    -Warren

    Mads Nissen commented  · 

    A feature long missing from Yammer should be architected for Teams: the ability to fusion and fission channels and allow admins to move messages.

    In an organic roll-out the sensible channel structure usually emerge organically, and your first hunch is wrong in 99% of cases. However, due to merging and splitting being super difficult people are forced to stay in the imprecise scopes of the original channels, decreasing the signal/noise effect.

    Like in the old SigOp days on BBS'es, and in old newsgroups, owners should be able to instructively move messages to other more appropriate channels when a user posts it in an irrelevant place.

    User Story:The teams owner selects Message(s) and clicks ellipsis to choose Move To -> *ChannelList* in order to place the message in the relevant channel.

    Secondly it should be possible to merge two channels seamlessly including history etc.

    Finally it would make sense to be able to select a bunch of messages and do Move To -> New Channel

    Mads Nissen supported this idea  · 
  7. 1,560 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    186 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Mads Nissen supported this idea  · 

Feedback and Knowledge Base