We have a channel with a tab with a Word document which lost a large comment I was working on because Teams/Word does not recognise and respect standard OS keyboard shortcuts.
Steps to reproduce:
1) Create a channel in Teams with a Word tab containing a Word document.
2) Add a comment to a piece of text in the document and start typing the comment.
3) Press alt+left arrow.
4) Teams will switch to the tab to the left of the Word tab silently loosing the comment with no obvious way to restore it.
This is problematic because a) Word silently looses data and b) Teams/Word does not respect OS keyboard shortcuts that are ingrained in user muscle memory.
Tested on Teams 1.0.00.28451, macOS 10.13
Thank you for the feedback, have you tried changing your Notifications under settings (you can find this by clicking on your picture in the lower left part of your screen). You can customize the type of notifications you receive from Teams.
This item is still under review by the feature team. I have no details as to when a decision might happen.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
When discussing in a thread it's way too easy to accidentally reply in the "Start new conversation" field instead of the "Reply" field, especially if you need to switch between discussions in multiple channels.
It would be less frustrating if Teams could e.g. hide the "Start new conversation" field while working in a thread.
Furthermore, Teams should remember the state of channel when switching between channels, including if I'm working in a thread. It's annoying that Teams has collapsed threads and removed keyboard focus from text fields when I return to a channel.
Unfortunately it was declined to decline this feature request.
Sorry to be the bearer of bad news.
Sometimes I receive emails notifying me about unread messages in channels, that I am in fact up to date in. Furthermore, the emails can arrive hours after the last activity in the channel.
This feature is still on the backlog.
The feature is still being worked upon. Many different changes are going into Teams and will provide a slow but steady pace to our performance increases.
I don’t have any new details at the moment but hope to get some additional feedback in the next several weeks.
There is a noticeable delay navigating between channels as well as switching between the Chat and Teams tab. This accumulates when I have to frequently switch between individual chats and team chats.
We are working on this!
This feature request is still being reviewed. The team is working hard to make numerous changes with regards to notifications, but they haven’t forgotten about this item.
I hope to have more details soon.
Currently we have Teams defaulted to show you the first (up to five) channels ever created. If you want to add more channels to your left rail view, just click the ellipses next to the channel name and select “Favorite”. When you favorite the channel, it will then be “pinned” to your left rail under that team name.
Try that and let me know if that meets your needs!
We’re fixing bugs identified in the comments, and other user reports we’ve received around markdown, but we’ve decided we’re not going to fundamentally change our markdown support.
This is the first time we’ve declined a request, and it didn’t come easily. We weighed this against other important features we’re working on to deliver and we had to make some tough choices.
Really appreciate your understanding on this, and please feel free to ping me if you have any questions, complaints, or need to rant.
The current markdown implementation formats text as I type. This is problematic when I want to change text or formatting as formatting boundaries are not visible and not editable. This leads to situations where I have to delete entire text blocks to change formatting og even get out of typing in e.g. all italics.
I would prefer that formatting takes place after messages have been typed, preferably on the receiving side so that the recipient can toggle formatting.