I am not sure if this is an edge case…. I’d love to know how others work.
On some calls – for example a managers meeting – you want to temporarily add in someone just for a quick question. You don’t want them to remain after the call. It is kind of a security or privacy issue if you don’t remove them.
So I find it really annoying when I forgot to remove them after the call and they probably find it annoying when they get our messages after the call. So I would prefer not to have to remove the person manually.
Suggestion – next to “Add people”, I think it would be really cool to add a person via an option “Add people (temporarily)”.
At SSW we are rolling out the use of the Approvals App with Teams to get requests approved through the organization. I love how easy it is to create templates and use them to submit requests. Previously we were using emails to manage these approvals, so another benefit is a reduction of noise across our collective inboxes.
Once an approval is submitted there is no way to alter the data. While this makes sense for requests that have been approved, it would be great if we could edit requested approvals prior to being approved. Currently, the only way we can do this is submit another request which means manually entering all information again which takes time.
Send another request with the updated information.
❌ This can be time consuming if multiple edits need to be made
❌ Copying information to another request can be error prone
❌ Approval system gets polluted with duplicate requests
Add the ability to edit an approval request prior to it being approved.
This would include changing the approver (if the template allowed the user to select approvers)
Every company has the need for requests to be approved. We’ve found that the Microsoft Teams Approval App works well, but only in simple cases. It is easy to create templates and use them to submit requests.
When companies switch from emails to a centralized structured approval, processes improve, and emails are reduced.
Senior Management are often responsible for approving most requests and as such can have a large backlog of requests to approve. In order to help approvers action the most important requests I would like to see the following enhancements:
Allow Priority to be set in Custom Approval Templates – ideally the priority level would be set in the Custom Approval Template, and not able to be changed by the user making the request.
The ‘Request title’ field is not enough. We need another column called ‘Approval Template Type’.
We can sort on the column titles, but we need the ability to filter by Priority and Approval Template Name
I work in the China office, and we keep reverting to WeChat because it offers this feature which is super useful. It is missing from Teams.
I want to be able to forward a group of messages in my private chat with someone else not in the chat. This often happens when a problem comes up in the discussion and I realized I have already discussed a similar issue. Therefore, I want to share a section of my chat history to them quickly.
❌ My current workarounds: Option 1: Copy + paste the messages one by one to the other chat. Option 2: Take a long screenshot of the chat history and share the image.
✅ Suggestion: Allow people to cherry-pick messages in their chat and forward them in a bundle.
We all love Microsoft Teams and I think this UI looks like it is about to be clever, but it is not.
When starting a new chat… If I pick 1 person… please attempt to guess the 2nd person I will add to the chat. People are often related and I know it would be a nice for all Microsoft Teams users if the people picker showed the like people that I will chat with together.
Today, it doesn’t matter who I pick first in the chat, the search always shows the same people.
Please pick who I will probably pick next … it should change the people based on who I am adding.
More info: Delve tells me who I talk to a bit, that would be ok. But when you talk to a manager, you probably are going to pick another manager. When I talk to an Azure DevOps engineer, I am probably going to pick another Azure engineer (not a React developer).