CTRL + Z Erases entire message
When typing a new message, pressing CTRL + Z erases the entire text you have written and replaces it with the contents of the previous message.
Pressing CTRL+SHIFT+Z or CTRL+Y does not restore the message.
The text is lost.
I experienced this problem already several times. Today, the consequences of this bug were just too painful, so I decided to drop this problem description here. The commit/roll-back feature in normal text message editing in Microsoft Teams seems flawed.
What I did: I entered text. Wanted to undo the last edit. Instead of undoing the last edit (I just entered a couple of words), the text jumped back to a much earlier state it was 15min ago. Trying to restore the message using CTRL+Y did not work!
This is the type of bug no word processing tool should ever be able to produce! Really frustrating!
I'm running 1.4.00.22265 (last update: 24.08.21), on MacOS 10.14.6
there's also the fact that when there's multiple people making edits, and one person decides to ctrl+z, there's a good chance he's going to roll back a change someone else has made at the same time. this is stupid. can microsoft fix this so that ctrl+z's are effective only on the work of the editor who uses it?
This is STILL the problem!!! I just typed 20 min of info to post to my teams channel, accidently formatted a word incorrectly, so, just like EVERY other MS product, I hit CTRL+Z to undo...but it REVERTS all of my work to a previous state from when I first started typing the message. ALL work lost. CTRL+Y does NOTHING. Why does it not do it's normal function of "REDO"????? Seriously MS? I've been in IT working in everything from support, to Admin, to VCIO/Consultant and NOW you decide to disrupt the common keystrokes used across all windows products? Did you let the same team that designed sharepoint work on Teams too? No excuse. Problem reported over 3 years ago here and STILL not resolved. Way to go.
PS - I'm careful not to type CTRL+Z here, bc I'm using Edge browser, who knows what it'll do...smh
João Olivença commented
It's stupid, and it does not make any sense!
The same problem exists in the text below a section of a Wiki.
Having lost a couple of hours worth of work, I may stop using this functionality.
A week of work was lost and unrecovered due to this issue. Since there is no change tracking or version control to recover from, this is fatal and completely unacceptable. Unfortunately this means the product is not mature enough for everyday use.