Matt

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

    3 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Matt commented  · 

    The "New conversation" button is sometimes out of reach from the keyboard. When I'm in an existing conversation, my existing habit is to hit esc, and arrow down to start a new message, but that it not working anymore.

    I can sometimes use the 'c' keyboard shortcut (after escaping from an existing convo) to start a new convo, but it doesn't work consistently, so I have to click the button or enter the Team list with cmd+3, then hit enter on the relevant channel, and then hit enter on the "New conversation" button.

    Matt shared this idea  · 
  2. 768 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    143 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Matt supported this idea  · 
  3. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Matt supported this idea  · 
  4. 1,797 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This item is still under review by the feature team. I have no details as to when a decision might happen.

    -Warren

    Matt supported this idea  · 
  5. 2,391 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    305 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Matt commented  · 

    This seems like a no-brainer. Other Electron (or similar) chat apps like Slack and HipChat have done this for some time, to very good effect. I strongly prefer a centralized,integrated notification tool over a medley of standalone options.

    Matt supported this idea  · 
  6. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Matt shared this idea  · 
  7. 2,659 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    216 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This request is still queued within our backlog. No new details yet.
    -Warren

    Matt supported this idea  · 
  8. 28 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 » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Matt supported this idea  · 
  9. 243 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    66 comments  ·  Public » Mac  ·  Flag idea as inappropriate…  ·  Admin →
    thank you!  ·  Warren responded

    I will be closing this topic since the feature request has been split apart into each individually requested item. This will allow you to see when items are actually closed out and moving ahead instead of having one item giving a perpetual misrepresentation of multiple pieces.

    Please take the time to vote for each of these you are impacted by.

    1) OSX client updates – app quits multiple times a day – https://microsoftteams.uservoice.com/forums/555103/suggestions/33838036

    2) MAC app fails to update with standard account (needs admin creds) – https://microsoftteams.uservoice.com/forums/555103/suggestions/33838069 (This item is completed)

    3) Update files are stored on the MAC taking up a lot of disk space – https://microsoftteams.uservoice.com/forums/555103/suggestions/33838114

    4) Need prompt before updating on MAChttps://microsoftteams.uservoice.com/forums/555103/suggestions/33838126

    5) After update on MAC – notifications are missed – https://microsoftteams.uservoice.com/forums/555103/suggestions/33838144 (This item is due to individual organizations not using modern authentication – once modern authentication is used, this issue will no longer…

    Matt commented  · 

    On most Macs I've tried, the automatic update framework is pretty aggressive, and apparently cannot be unconfigured. However, it consistently fails to update the app when I'm logged in with a standard account. The app occasionally prompts for admin creds (I assume it's making an update helper daemon), and I supply them, but the only Helper process Teams ever runs is owned by the standard account. I'm not sure exactly what to suggest here, because there are several opportunities for change, some of which might obviate usefulness of others. Ideas might be some user interaction to defer the forced relaunch during updates, options for scheduling deferred updates, options to manually supply admin credentials at each update, improve reliability around whatever helper proc is supposed to facilitate updates.

    Matt supported this idea  · 
  10. 30 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Mac  ·  Flag idea as inappropriate…  ·  Admin →
    Matt shared this idea  · 

Feedback and Knowledge Base