Drag chat messages to merge them into one reply thread
Since a lot of people type messages in quick succession, it'd be helpful to have the ability to drag and merge them together into individual "reply threads".
Thanks everyone for the clarifications to this request. Upon further technical review, we have decided to decline this request at this time.
Please continue to contribute your ideas — they push us to innovate, problem solve, and really understand your needs.
Need this or at least a way to merge, critical to keeping a clean and structured Conversation tab.
Decline message sounds more like "To Hard; Didn't try"
Steve Dohm commented
Hang on, declined at this point???? Teams was designed for internal company communication. There is functionality to pull external communication (email) into internal communication. When there are multiple external communications that need to be included in one internal discussion, it stands to reason that CONVERSATIONS MUST BE COMBINED FOR ORGANIZATIONAL PURPOSES. This is a bigger issue than making a mistake and combining. Please reconsider the decision to decline this mission-critical request.
Please combine with the other suggestions along this same topic - there are likely much greater than 375 folks in support of this type of feature.
At least consider enabling Team Admins to "fix" broken threads when users have accidentally started new conversations by using the large text box instead of clicking the small "Reply" link.
This is probably the biggest weakness that Teams has right now. The interface is confusing and most people end up creating a new conversation instead of replying. The channel quickly turns into Chatter... This ability to cleanup conversations is desperately needed!
They decline the idea to merge conversations on Teams in a merged thread on UserVoice. Interesting.
Still have a need for this.
John Carlson commented
Did I get this straight?
"Please continue to contribute your ideas — they push us to innovate, problem solve, and really understand your needs."
Is on a declined feature request?
I have an immediate need for this feature. Contributors in our company are from around the world and start conversations about topics on local levels. We need to consolidate those conversations so that as a company we have one correct company decision, not fifteen approaches.
I understand that somethings are difficult to implement. I understand that everything cannot be done in the next release. I understand the many times the architecture must be rewritten to support a single new feature. These are all valid reasons that some things do not get implemented, and with the latter, may never get implemented.
So, from the, "we have decided to decline" comment , I must assume that this is so difficult that it cannot be solved.
I am throwing down the gauntlet. Any takers for solving this particular problem?
Paul Noble commented
even if the reply/new convo is resolved the needs to merge conversations will still exist
Don Lauer commented
Fingers crossed that other GUI updates address user confusion around where and how to respond. As an owner and member, I could have used this feature countless times in Teams and Yammer to correct improper behavior.
This feature should be implemented, this occurs all the time.
Robert Arnold commented
We also have this problem. Could we please have an change to allow a solution to this other than a delete and paste back to the appropriate conversation thread.
Sean Ellis commented
Even though the changes to "reply" vs "start a new conversation" will hopefully reduce the need for this feature, it is still useful.
Paul Noble commented
this is the number 1 request we get for every new user onto the application platform, it'd immediately solve all the 'new conversations' vs 'reply' issues and make the program more adaptable and usable. The declining of features like this and the other obvious QoL usability requests such as chat resorting, auto scrolling etc, drag and drop - things that programs have had for years as standard are the types of missing features that will turn off user uptake and put people off using it long term.
James Arber commented
Looks like there has been an update to this request that makes this redundant
James Arber commented
Suphatra, I assume that the request is difficult to implement hence the decline for this request. But will there be some kinda of fix to stop spurious threads that occur in the Desktop client? I see this in my tenant and in my customers to the point its becoming a meme like Discords "@Everyone" meme.
Geraldine S commented
hmmm not very happy about this decline. Can you address the fact that the UI is not very obvious for users so they can't distinguish between a new post or a reply to an existing thread... this confusion also comes from the fact that in Private group Chats it is one continuous thread
Mike OConnor commented
If not a way to merge, then some other method to pull errant replies back into the correct thread. Having random replies that become disjointed within a channel is bothersome at best, but can lead to loss of pertinent information that gets lost or worse.
Ditto on make the UI to avoid these better
Marvin Dickhaus commented
If you're declining this idea, please optimize the UI such that those mistakes just don't happen in the future.
Bummer this was declined! Our organization was really looking forward to this. Probably the single most important request for us right now. Also, there is very little context on the rationale for this decision which makes it a little more difficult on our end too.
i started a new thread asking who want's to have a beer after work.
5 people started new threads instead of replying to the existing one.
this suggestion needs to happen.