13 votesBBB shared this idea ·
This item is still under review. No new updates at this time.
This item is still on the backlog. I will continue to track this item and provide updates as soon as I get new updates.
This item is still in the queue. I’m still awaiting more feedback and hope to have more details to share soon.
I really like the suggestion of creating an alarm on a message, so you come back to it. I’ve passed this on to our engineering team.
Meanwhile, here’s another feature you can utilize for the same purpose — use our “bookmark” button, which is in the upper right corner of every message. This will save that message or thread directly to your profile. To access your saved messages, just click your face in the upper left corner of the product. You’ll see a tab in the left rail that says “Saved.” This is like a list of little reminders.
Hope that helps! :-)
We have raised the priority of this work item, and it is currently being worked on. We don’t have any dates to share at this point, but will update when we have new status. Thank you!
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.
Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.
This is currently in internal testing rings at Microsoft, and the feature team is targeting a release to the public in early Q2.
~Alex & the Teams team
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.