I never experienced any crashes, and neither can I recall a team mate complaining about that.
Bugs I encountered:
1. Opening the link to a scheduled meeting opens the browser (good), but then clicking the "open in teams" and confirming the external URL handler in the browser does... Nothing. Restarting teams fixes that. (Happens for my team mates as well).
2. I have a dedicated USB mic that's always on, while my speakers are on a different USB device that's not always on. I have to reconfigure the audio settings very often, which is especially annoying since I can't do that before answering a call. But changing the audio device works without error (unlike Discord on my private PC, which lets me select the newly connected USB device as output, but needs to be restarted to actually output audio to it).
That's about it. Of course memory and CPU usage are rather impressive. And afaik we don't use the phone (as in landline, not as in app) feature; at least I don't, so I can't comment on that.
I've to add: I tend to bash MS first and ask questions later. I'm unhappy I can't use Linux on both my work PCs. But if I'm honest, teams works pretty well for us.
Have you never sent a message with images just to later find out that the message wasn't sent and it wouldn't even show up on the chat so you could retry?
Have you never tried to join a meeting where teams made you just sit there for a minute until you decide to restart it?
Have you ever called someone at the same time as they call you, ending you with teams saying that they are calling you at the same time as you are calling them?
Have you ever tried to click on an old message from a search result, just to end up nowhere near the message?
Have you never join late to a meeting because teams didn't notify you that the meeting had started?
If you have an external calendar account linked to outlook, have you never noticed that the linked calendar events don't show up on teams calendar?
Have you ever clicked on a message notification, scrolled a bit up or down to a different message and have teams snap you back to the notification message for no good reason?
Have you ever thought to yourself that it would be nice to use custom background images on video calls, just to realise that Microsoft loves Linux so much that you can't do that on their Linux client?
Have you never noticed your teams status showing that you are in a meeting when you are not, even without any schedules meeting in the calendar?
Now that you say it, I might have lost an image once?
Maybe our usage is just to basic; it's a tool for voice/video calls/meetings and some basic chatting. We can't even attach files anymore because our company doesn't really use teams and didn't extend the necessary licence (only our team/suborg is allowed to use it, since we need something like it and the internal alternative is not built, yet... Don't ask, not my paygrade to decide or influence that).
I don't do a lot of searching. Maybe it's broken, maybe not. Wouldn't be too surprised if it is for some users and works okay for others.
Meetings are in our outlook calendar, with working notifications.
No idea about my status, never noticed it to be off.
I'd happily trade Windows for Linux if that meant no custom background images. But I'm not surprised that the Linux client is more limited.
I'm probably just lucky we use teams only a little.
I have experienced several things on that list, a long time ago. I haven't lost an image in the past year. It seems these days when I call someone when they're calling me it just connects and works and connects. I don't have issues with missed notifications. I'm using the Windows client though.
That bit about connecting when two people call at the same time just happened to me as well yesterday, so it seems things are improving, albeit slowly (better than no improvements).
> I have to reconfigure the audio settings very often, which is especially annoying since I can't do that before answering a call.
A similar issue occurs on Skype for Enterprise. You cannot plug your headphones in after someone starts calling. You have to decline the call, go in the settings and call back.
Bugs I encountered:
1. Opening the link to a scheduled meeting opens the browser (good), but then clicking the "open in teams" and confirming the external URL handler in the browser does... Nothing. Restarting teams fixes that. (Happens for my team mates as well).
2. I have a dedicated USB mic that's always on, while my speakers are on a different USB device that's not always on. I have to reconfigure the audio settings very often, which is especially annoying since I can't do that before answering a call. But changing the audio device works without error (unlike Discord on my private PC, which lets me select the newly connected USB device as output, but needs to be restarted to actually output audio to it).
That's about it. Of course memory and CPU usage are rather impressive. And afaik we don't use the phone (as in landline, not as in app) feature; at least I don't, so I can't comment on that.
I've to add: I tend to bash MS first and ask questions later. I'm unhappy I can't use Linux on both my work PCs. But if I'm honest, teams works pretty well for us.