Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Tell me you're a Developer that doesn't use your own product without telling me you're a Developer that doesn't use your own product.
You remove, not modify options for, but COMPLETELY remove basic/common functionality for power daily users (or even standard users in some cases). You did it "to save time". Let's see...how much more time does it take to completely retype a name (e.g., Obilisetty VijayKumar, sorry 😬), GET IT CORRECT and type a date/timestamp with special characters vs. how long it takes to delete a line?
Additionally, trying to use the workaround on the initial sender is flawed and difficult because the reactions pops up directly over this info as soon as you hover over it and doesn't go away, so I'm not sure if I have all of it until I paste it and I don't. I swear this must be new because I've been using the workaround to copy it and I would have noticed this before.
As @Kevin Wudtke pointed out, NOT including the sender and timestamp vs. 313 votes to bring back the functionality is (updated) 12 vs. 314, AND MOST OF THE COMMENTS ON THE NO VOTE ARE TO BRING IT BACK. This was simply bad, ignorant design, which was probably done because it was low hanging fruit that presented the opportunity to pretend like they're listening to feedback.