Allow copying whole chat conversations
Currently, it's not possible to select & copy more than one message in a chat. When I try to select two or more messages, the focus stays on the first message making it impossible to copy whole chat.
There are some really ugly workarounds like: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Copying-conversations/td-p/62849 which I don't consider a solution of the situation.
I want to be able to select multiple messages at once and copy them by hitting CTRL+C.
Thank you for your suggestion! We really appreciate the feedback and idea. We have reviewed this request and started working on it. I’ll let you know as it nears completion.
2 years later - still nothing is done to solve this issue. Can we please have a solution.
C Tomas commented
I agree, I regularly rely on that capability on Skype and wish it was available now that my workplace is transitioning to Teams.
Peter Spielvogel commented
Being able to copy full chat would be very helpful.
Don Matulek commented
Any status update two years later?
So where is the solution. Two years on this feature is still not possible. Disgraceful. I do not like Teams but this missing function makes me dislike it even more.
Two year anniversary of "working on it"
Sammy F. commented
- Click the start of the conversation (right before the name of the person who initiated the chat).
- Scroll down to where you want the selection to stop, hold down SHIFT then click there.
-The conversation will be selected.
- CTRL + C
Status update or something?
I takes so much time to get a conversation out of teams so I can share it with my ... team. Is everyone at MS using slack? I can't fathom that this isn't something that is being asked for internally as well. There must be some way for me to copy/export these messages. "Working on it" for 2 years?? MADNESS.
Having a transcript of the chat is fundamental for meetings. Not everyone in our meetings is internal and can go back and check the chat.
If you highlight all the text in the conversation, then Ctrl-A, then Ctrl-C, then Ctrl-V it should work
Suphatra, is this really going to get done? How can this take 2 years to complete?
Not being able to save conversations makes TEAMS my most hated application ever.
I am pushing management to get off this product due to its poor feature design.
If this get done before I get my way and we move to Slack be sure it allow export of ALL conversations, not just Teams conversations.
I am amazed and disappointed it has taken this long . . . but not surprised. MS is too big and customer satisfaction is no longer important because they have the market. This is always the first failure of a monopoly.
Really really poor feature to not allow more than 10 or so messages at a time. This is a basic and should have been completed upon development. Business will have to rely on this and you have no provided an update for 2 years.
This is a key feature of any chat application and is preventing me from using microsoft team in the first place
I agree, I would really like to have a copy of my chat as I am using Microsoft Teams to teach at work
Donald Prescott commented
It's been 4 years now - literally every other MSoft app allows CTRL-A or copying multiple pages. What gives Teams being blacklisted from this?
Please enable copy and paste messages on the chat. This is so annoying and even workaround does not work.
I work in a help desk. We often use teams as a backup method to contact the user when the chat drops in out default chat application (restart the computer, a BSOD, connection interrupted, etc.)
And we need to copy&paste the conversation held in teams, so we can archive the whole case.
Currently, the select text works randomly (sometimes it works and some others only parts of the text are copied, not the entire conversation and have to stay copying and pasting multiple parts of it...
Really, is that hard to just allow the text copying as in any other application, like skype?
This is a MUST!
Microsoft never stops just blowing me away. I hope a competitor can unseat them someday.
Andy Evans commented
This really needs to be addressed. None of the workarounds are really suitable.