This request is still queued within our backlog. No new details yet.
This feature is under review by the feature team. No new feedback at this time.
An error occurred while saving the commentBearMef 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?
This continues to be on our backlog due to prioritization of other work items. We will update when there is more to share.
This item remains on the backlog.
Thank you for your continued feedback! We are excited to announce we are currently testing this feature internally. We will share an update as soon as it is available.
We are working on a design with more density in mind. Until this design is solidified we are putting this item back to Under Review.
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.