Teams Chat - copy/paste

I don't copy and paste from Teams much, but when I do, I want to make a record of a conversation for technical purposes. It is absolutely ridiculous to not save the names and timestamps of the people involved in a conversation when you cut and paste. The names of the people talking are the delimiters of what is a "conversation" between people. I can't imagine why such a stupid decision was made at Microsoft to remove the ability to keep this information. It is/was an idiotic decision. Please fix. Please fix. Calling the persons making the discussion "Metadata" is absurd. While a programmer may refer to it as Metadata since it is not the actual text, it is clearly not "Metadata" from the point of something being a conversation. It is like someone taking a selfie picture, but removing the actual person from the photo because they were also the photographer and thus should be removed since it is "metadata" tag. (Or, if you took a picture of a sign saying Columbus Ohio, and removing the name on the sign because it was "metadata".) Please programmers at Microsoft, don't try to be software smart but practically stupid. Capturing the record of a conversation should almost always include the names of the people doing the conversation to be useful and pretty much the only reason to not include those names is if you are trying to anonymize them. Even in the latter case, you would substitute names (e.g. person A, person B) to track multiple entities weighing in, and that anonymizing should be left to the person after capturing the conversation.

I too want to comment that this removal of an existing functionality/feature should have been defined as configurable to those supposed users that didn't want the clutter. I want the name and date/timestamps back when I copy chat threads for documentation purposes into Jira. I would have preferred to have just removed the likes and reactions when copying and pasting but once again that should have been configurable option in my opinion. Please get this to appropriate resources to address.

Yes, it is punishing! I had to download a full page screen shot add-in for google chrome to snippet conversations. (But it's not good because now i'm saving images of conversations, not the text to copy/paste) I run a construction company and we do tenders, a lot of tenders, largish 1-10 million range, and we have a tender chat for each tender. It's critical to be able to show a supervisor taking on a big job, what we considered during the tender phase, so they can quickly get up to speed around tricky detail and allowances. I do wonder if it's deliberate, not allowing a copy paste of entire chats due to some kind of privacy clause. Any who, looking forward to an update here!

I see I'm in good company looking for a solution for this issue. This is a poor design choice which could have simply been made optional via a configuration setting rather than removing it entirely.

There are many, many valid reasons for letting users copy the entire chat stream with details in place. Not the least that the function existed already and people were clearly using it.

I work in the accessibility area and meeting participants will often provide very useful commentary via chat - some because of their own accessibility requirements. Other users need to copy the chat out to an external document to be able to access it in the way they normally work because of their disability. Removing the names and timestamps creates even more barriers for people with disability and removes important contextual information.

Giant thumbs down on accessibility and equity Microsoft!
Perhaps Microsoft could think about the collective time and money spent by MS clients trying to resolve this simple issue?

The suggested workaround does not work and is not a solution.

The "noise" has been replaced by "garbage" that requires even more time to reformat, amend and fix to be useful.

Please look at this seriously Microsoft and provide a solution that is effective.

I want this feature back!!