Jul 13 2023 08:31 AM
Jul 13 2023 08:31 AM
This is a long standing defect in the preview client that has existed since launch.
When a new chat message notification appears (i.e. windows notification) and I click on the notification to go to the chat, but instead of going to the chat in the teams main window, it spawns a new pop out chat window. I have the "Open new chat in" option set to "Main window". The expected behavior would be to open the chat using the user preference, which in my case is Main window.
The result of this incorrect behavior is if I click on the notification (out of habit because thats what notifications are for) then it pops a new window which I then have to close, after which I manually pop the main window and then find the chat in question. This defeats the entire point of the notification which is quick access to the chat in question.
Its incredibly obnoxious. Theres also a bug in the teams feedback that flags this as expected behavior which is not correct.
Jul 14 2023 02:38 AM - last edited on Jul 20 2023 10:37 AM by EmilyPerina
Thanks for reaching out about the issue with Teams preview. I totally get how annoying it is when clicking on chat notifications opens a new window instead of going to the main Teams window.
But guess what? Our team knows about this long-standing defect and we're on it! We're working hard to fix it ASAP and give you a better experience. We're sorry for any inconvenience caused.
Jul 20 2023 06:55 AM
Jul 24 2023 02:13 PM
@edevcn , where is this magical setting??? This would save a lot of daily cussing on my part if I can get this working. I'm using this version:
Jul 24 2023 04:57 PM
@DotNetCoderDFW You'll find it in the 'General' section of your settings under 'Open new chat in'
Aug 24 2023 01:47 AM
I'm sorry, but the setting doesn't work for me for the chat's opened from mail notifications. Even if I choose "Main window", the "Go to conversation" link in the mail still opens in a new window. Is there any fix available for this?
Aug 29 2023 07:08 PM
@Alina_Maria Hmm that one, I'm not sure, sorry. It could be the way it's handling deeplinks from emails.
Best to give feedback via the Help menu if you think it needs to be resolved.