this feature would have been tremendously handy for a long and important Group Chat that eventually got converted to a Channel. We could've exported the chat dialogue into a document (or even just a simple txt file) and uploaded into Files. Trying to copy out the text manually into an editor is very tedious, and we don't want folks referring back to the Group Chat.
Our scenario is, of course, best served by enabling a Group Chat to Channel conversion feature.
This item is still under review. No new updates at this time.
The comment from Daniel made on July 25, 2019 09:02 is particularly well expressed regarding the scenario, and this feature ask.
This would be a really nice feature to see included in Teams. It would've made our migration over to Teams (from Slack) a lot easier. Often, we would start out in a Chat that grew in terms of both audience and long-term strategic need, and at a certain point converting the dialogue to a Channel made more sense over persisting it in a Group Chat.
This item is still under review. I’ll keep following up with the feature team and sharing all your feedback.
Where are we with the review of this feature request? Our organization is moving over to Teams from Slack, and Slack has amazing capabilities for customizing audio and notifications. This has been a major regression for our users, many of whom work remotely and rely on audible notifications (think LOUD) from this primary communications medium (i.e., Teams) to make them aware of critical updates, notifications (e.g., from alerting systems or our ticketing system where we have connectors/bots), and conversations.
Please provide an update on this feature topic.
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! :-)
Ok...how about the capability for being reminded about a Saved Message? While helpful, simply adding it to Saved Messages isn't really meeting the feature bar - we need the reminder, and a notification. Our company is transitioning to Teams from Slack, where we found the /remind feature incredibly useful for a variety of scenarios. We've cobbled together an MVP solution using a Flow to send a reminder message to a channel after x minutes (along with a Flow Notification), but it's very stopgap while we figure out a better solution.
This feature request is now under review.
I’ll update this topic as we move through the decision process. Thank you for the suggestion.
@Teams Feature Team - I see this is "Declined". /Please/ reconsider this request for adoption in the Product UX.
This is a standard feature to reduce distraction in your competitors products. For those of us coming from those products into Teams, this is a noteworthy departure, as previous comments here reflect.
please consider this submission as part of this request, https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32693563-1-allow-me-to-refer-to-group-members-with-their-f
The fact that Teams is drawing from the company-defined GAL and using the Display Name field (where I work the Corp IT team has elected to use the Lastname, Firstname methodology, which is awful UX within Teams) needs rethinking. If the Teams product can override this and always ensure "Firstname Lastname", it will provide a much more personalized (i.e., normal human) experience over "Lastname, Firstname".
Please provide an override to the Enterprise GAL configuration so that Teams always shows the users in Firstname Lastname orientation.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
Slack will serve as an excellent guide for pretty much what everyone here is upvoting.
Unless I'm mistaken, /this/ submission is far-and-away the most "Voted" feature request for Teams in the uservoice (not to mentioned that there are a bunch of other submissions which basically echo this submission). Getting this implemented into the UX will be a monumental improvement!
Hi Forum Admin! Just checking in to see if you're able to share an update on this feature submission, and its place on the roadmap. Our group is migrating from Slack to Teams, and this is one aspect that would really smooth the transition for our users. Screen "real estate", especially on laptops and mobile devices, is at a premium so we're excited to know that improvements are in the works.