Anonymous
My feedback
-
88 votesAnonymous
supported this idea
·
-
5 votesAnonymous
supported this idea
·
An error occurred while saving the comment -
4,842 votes
Adding any emoji as a reaction remains under review.
I am marking this as partially done to let you know a new reactions bar with Like, Heart, Laugh, Surprised, Sad, and Angry has begun rolling out to all users.
Anonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
another vote here.
Need to have possibility to use any of existing smiles to make reaction on the messages. If project managers can not invent smth new, just take a look at the slack implementation. Very handy.
and even better, if would be possible to add reaction on the message through the API as well (in case if this feature https://microsoftteams.uservoice.com/forums/555103-public/suggestions/19199878-allow-to-post-a-reply-to-a-conversation-via-rest is finally implemented).
-
301 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
under "review" for years? sounds like a real MS support. Neither feedback, nor a feature or at least proper docs how to do it.
but to have it, would be really great to easy reply on message. As a use case: during deployment/testing you open thread and then during script execution, append new messages in the thread.
+1 here. it's really needed. It's a huge usability improvement and a great time saver, when uses smart search!
just see slack as example how it's implemented. Even in Jira/Confluence similar is implemented.
As a simple use case we have a lot of employees in the company and multiple teams in the corporate account.
When we type user, we use quite actively @mention to speed up typing process. E.g "@personA knows this functionality, please contact him in person" or "I have asked @personB ....." , etc..
So on. It's not needed and not mandatory that mentioned person must receive notification that he/she was mentioned in team's channel, where he/she has no access to, but rather needed for usability purposes. Because:
a. when you click on mentioned person, you can open a private channel with person so on.
b. you can use autocomplete functionality to put username in message without too much typing and point of particular person to avoid any misunderstandings
b. Especially it's very helpful, when you have in one company more than one person with same name or/and surname. In this case you need to type MANUALLY both first name and last name, so on.
I do not want to tell smth bad about MS Teams and I like a very good integration with other MS products I use, e.g calendar and outlook, but if you compare it with other products, sometimes you feel that MS Teams from the stone age or UX designers are too busy with "fancy whizzes".. so that in the UserVoice we see many requests waiting for votes for years, while same functionality implemented in the competitors.