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.
Johan Vendrig commented
from my perspective this is about conversations within a team/channel where people will often by mistake use the "start new conversation" box at the bottom of the screen, rather than the "reply" box at the bottom of a conversation - in those instances it would be great if you could move those messages to the correct conversation so the thread doesn't get broken and the comment doesn't get lost.
given you don't have threads in 1-1 chat then it doesn't apply.
So yes its about moving a reply to a thread in a channel discussion.
If you had threads in 1-1 chat it would apply to that too.
Andrew Robinson commented
For me this is being able to attach new threads in a channel into an existing thread. People are constantly typing new messages instead of hitting reply. Drives admins crazy as you end up with floating out of context messages!
I see this has merged - definitely need a way to organize the flow of threads, especially when folks don't click "reply" in the correct location and it results in a truncated, separate or new threads.
Admins should have the ability to move all the comments around, members should be able to move their own .
SO glad this is under review. While i think some of the UI changes proposed below might help, i think the functionality needs to be addressed that would allow for two threads to be merged back together. UI won't get it all the way done.
Perhaps to get around this, it would make more sense for the "thread reply field" to be more clearly differentiated from the "new thread field". Even having the existing thread and its reply field indented (as compared to the new thread field) would make this a clearer distinction.
Using both the Mac and PC clients.
Also allow "Owner" to do this on a Member message.
I imagine it as the ability to grab the orphan post and drag it up to snap it to the correct thread - or even to a point within the thread that makes sense... but the default location in the thread could be by time-stamp.
Please address this. This frustrates our users to no end, especially in busy channels where grouping the thread is very important.
Nick George commented
People do this all the time...… all. the. time.
Marc LaFleur commented
This has become a consistent problem, particularly in larger Teams. We regularly find multiple "threads" that stem from miss-parented replies. The ability to "re-parent" would allow moderators to clean this up without having to request the user delete/replace.
I think the best way to accomplish this would be to add another option to the ... menu on a conversation that reads something like "Move to previous conversation". This is the menu I need to go to in order to delete the conversation I mistakenly created after I've moved my comment to the end of the previous conversation. Making this a one-click action would be great!
It really is far too easy to start a new thread vs reply to the intended thread. Hopefully this idea gains enough traction to get the product group's attention!
Scot Witt commented
Amen, Brother, horrible UI.
Jamie Thomson commented
This request is basically a clone of https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32684689-combine-conversations. Please can you merge them together.
Jamie Thomson commented
I came on here to as for exactly this, thank you to the person that already raised it.
This is definitely a problem - I often see people starting new conversations when they should be replying to existing ones. Its clearly an accident on their part but given it happens so often (and believe me, it does) I'm led to believe that the UI is somewhat to blame. Its not just novice users that do it either, I've seen extremely IT-literate people that are experienced in using Teams making the same mistake.
I find the problem occurs more often when people are replying via a phone app, the distinction there between replying to a new conversation starting a new one is less pronounced.
I think the ability to merge conversations together would be really useful. I suggest the following rules around it:
- 2 conversations can only be merged if they are in the same channel
- Conversation merging can only be done either by the person that started the conversation that is going to be merged, or by a team owner
-If the two conversations each have many messages then the resulting merged conversation might be even messier than when they were separate (due to messages from both conversations being mixed together). The person doing the merge should have the opportunity to preview what the merged conversation would look like.
My friend Jack wants this too! :D
Mariel Haddad commented
We have the same issue in our teams
We often have people accidentally create a new thread when intending to respond to an existing thread. It would be nice if we could drag that new thread into a previous one (where intended).
Yves Rausch commented
Very often me and other people in the team answers to a thread in wrong input (new thread). Instead of answer to an existing thread they start a new one then.
After doing this I want to be able to move such an answer to an existing thread to correct this.
This is even useful if I want to merge to threads into one...