BearMef

My feedback

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

    We’ll send you updates on this idea

    272 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

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

    We’ll send you updates on this idea

    138 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This feature is under review by the feature team. No new feedback at this time.
    -Warren

    BearMef supported this idea  · 
  3. 1,159 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    149 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    BearMef commented  · 

    Hi MS Team!

    I wonder the approach you have, doing [clones of] something. The Slack team is promoting the ability to send a message to yourself as a one of the cool feature of their messenger and it's really helpful - you can find many "thanks" for Slack team for that feature.

    It's definitely was a requirement for Teams application to _exclude_ yourself from the list of message recipients and it's definitely additional efforts to implement it. So, product owner / project manager / analyst (all of them) spent time to decide to create and describe this requirement; developer(s) implemented; QA team run tests and, sure, it had been documented. All of that is just to, intentionally, kill the useful feature spending additional money for that.
    I assume that implementing the messaging to yourself will require efforts to avoid some specific side effects at the platform/app, but is it so complex and more benefitable to kill the feature, especially when you have a brilliant example to follow by?

    Can you, guys, explain it?

    BearMef supported this idea  · 
  4. 21,168 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2523 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    BearMef supported this idea  · 
  5. 14,531 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    822 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    BearMef supported this idea  · 
  6. 11,342 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    421 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    BearMef supported this idea  · 
  7. 16,454 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1581 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    BearMef supported this idea  · 
  8. 591 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    116 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This request is still being considered by the feature team but a final decision has not yet been made. I’m still awaiting more details.

    -Warren

    BearMef supported this idea  · 

Feedback and Knowledge Base