Jake Moore

My feedback

  1. 22 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  2. 5,683 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    595 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    It has been three months since the last update, so checking in here to let you know this is still being actively worked on. I really appreciate your patience as we work on this.

    I hope you’re all enjoying the holidays, and have a very Happy New Year!

    Thanks,
    Suphatra

    Jake Moore supported this idea  · 
  3. 8,514 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    720 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  4. 7,161 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    827 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  5. 16 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore shared this idea  · 
  6. 3,207 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    121 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.

    Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.

    Suphatra

    Jake Moore supported this idea  · 
  7. 3,592 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This feature request is still on in the backlog. No new updates available at this time.

    -Warren

    Jake Moore supported this idea  · 
  8. 1,216 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    154 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  9. 1,444 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    70 comments  ·  Public » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  10. 2,250 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    66 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
    Hopefully this will move back up in the queue soon.

    -Warren

    Jake Moore supported this idea  · 
  11. 4,117 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.

    -Warren

    Jake Moore supported this idea  · 
  12. 5,346 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    working on it  ·  340 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  13. 8,852 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1056 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  14. 823 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    123 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Warren responded

    Mute a channel is still being worked upon. The team is still hard at work on this item. No updates at this time.

    -Warren

    Jake Moore supported this idea  · 
  15. 19,442 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1633 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore commented  · 

    Great, this will really help me achieve what I need to! Thanks for sharing the intention

    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel this would solve my problem. Nested teams with the ability to set permissions for each nested team could work too.

    Jake Moore supported this idea  · 
  16. 7,093 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    475 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    Unfortunately due to re-prioritization this item has slipped back onto the “backlog” for the time being.

    I hope to see it move back into “working on it” soon and will continue to engage the feature team with your feedback.
    -Warren

    Jake Moore supported this idea  · 
  17. 259 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Public » Admin Tools  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    Thank you all very much for the great response. The survey is now closed. The feature team will be reviewing all the data that was gathered and responded based on the findings.
    Again, thank you for helping us make Microsoft Teams the best it can be.
    -Warren

    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel then this would solve my problem.

  18. 1,045 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    140 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Warren responded

    This request has been reviewed and declined by the feature team.

    You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.

    -Warren

    Jake Moore supported this idea  · 
    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. If I could nest teams that would be helpful. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel then this could be an option too however, greater nesting would indeed be super helpful.

  19. 948 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    declined  ·  135 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  20. 3,831 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    363 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore commented  · 

    It seems that threads get posted in the incorrect channel because people dont know where to post at times or forget that a channel exists. It would be beneficial to the overall tidiness of teams to be able to move a thread from one channel to another if someone posts it in the incorrect place.

    Jake Moore supported this idea  · 

Feedback and Knowledge Base