Teams Chat - copy/paste

Quick question to Microsoft - Why is the MASSIVE amount of negative feedback regarding this change being ignored?

We're told to post feedback to get changes considered by Microsoft. This has been done on countless occasions.

We're told to upvote feedback posts to get greater consideration. Some of those posts have enormous amounts of upvotes.

However, to date I have seen no acknowledgement from Microsoft that this is an issue that they need to address. I understand that there were a few people that wanted this change to begin with but there was no consideration about the countless others who need the metadata. This was a gross overcorrection and if a simple switch cannot be added to settings for users to select how they want copy/paste to work, it should be reverted! At least before the few people who did not want the data could choose to delete it. Now we have NO OPTION AVAILABLE to get this data.

MS's behaviour is another example that monopolists do not care. I am not sure anyone at MS is actually even assigned to analyzing the feedback from the users. Even if there's, it's likely to be a n outside vendor somewhere in India whose management is not interested in sending negative f/back to the HQ because the "bosses" do not like seeing negative things.

THis option stopped working a few weeks ago and I have not been able to identify another solution. The forward feature is ***********ABSOLUTELY********** useless!!!!!! No one has to only capture a time stamp on a single message. We have to capture discussions that sometimes span a week or more. Microsoft please do something to correct this and provide a workflow to capture with and without metadata. THIS IS URGENT AND CAUSING SERIOUS PROBLEMS FOR CORPORATE USERS!!!!!!!!!!!!!

Adding my vote, my bemusement, my incredulity, my dismay.

Yes, there were times I didn't want the clutter. But there are also moments particularly in a long chat where it's reasonable to want to know who said what and when. It may be for business records, or perhaps when assembling an argument.

I wonder if this is a grand fail of product feedback... some users said "I want to able to cut and paste without clutter" and the whole design process proceeded in the same way they would a split test over whether a log out button should at the top right, or top left.

ie that the answer is one or the other. In this case the right answer is both - because it supports different use cases.

Bleurgh,

I want this feature back!!