Add ability to move mistaken thread replies in a channel to the intended thread
If a user misses replying to a thread in a channel and instead replies directly to the channel, this message is not part of the thread that it was intended to be and the conversation is not clear.
There should be a way for a user or channel admin to move a message to the intended thread inside the channel and keep it inline with the on-going threaded conversation (since everything is timestamped this seems possible).
This would clean up the conversations and mistakes that users will make.
Christopher Johnson
shared this idea
Work on this feature has begun! Big thanks to @kkekkonen for starting the effort.
If anyone would be interested testing it, you can help out here: https://github.com/mattermost/mattermost-server/pull/9165
PS: Previous update incorrectly mentioned that this an Enterprise Edition feature.
-
Ryan Fleming commented
This would address one of the most common complaints I hear in my MM user community: we need to be able to move messages into, out-of and between threads that may be on different channels (though IMHO, the case of needing to move message between channels is less common: usually the message is just forwarded to a different channel).
-
Kurbi et Korbi commented
Any updates? This would be a real pain relief for any organization using threads
-
Silvan Wehrli
commented
This feature is highly wished. It happens almost daily that people just write in the channel instead of using the reply functionality.
Other option is to have the reply button always visible and better visible -
Scott
commented
We so do...!
-
Ioannis Cherouvim
commented
We need this!
-
Anonymous
commented
please merge this...
-
Brendon Alexander Roberto commented
I would also love this feature, it's very easy to forget to make a reply within a thread and when it happens a lot, it makes following threads difficult.
As a channel admin, I'd like the ability to quickly and easily fix up the threads in the channels I manage when users forget to reply to threads correctly.
-
MailYouLater
commented
I asked on the linked GitHub issue, and jasonblais responded "we continue to monitor the feedback and votes in the feature proposal forum", so I guess that means that if they see more votes on here they'll take another look? IDK, but I hope so.
Everybody: Please vote for this feature!
-
Arne Kvalnes
commented
Not sure about status here? According to information in the link referenced above, work is stopped?
-
Meta
commented
This is a very good feature that's been missing! A lot of people in my company don't get the thread function and it'd be a mess to move these messages manually if I really wanted to clean those up!
-
Fermulator
commented
@kkekkonen - ack why fork!? - pull it into mainline Mattermost please ;)
-
Very interesting! Thanks for sharing these Kaarlo.
Would you be interested joining https://pre-release.mattermost.com, which is a public server for Mattermost community and staff?
It would be great to get you in touch with some of our team members and see if it makes sense to have this feature in the product as well. I think there's been some discussion about moving conversations in Mattermost.
-
Kaarlo Kekkonen
commented
Its built in on a mattermost fork, Unfortunately I didn't see a way to turn it into a plugin. It would be neat to add it to mattermost, or at least get some ideas for improvement.
It can be accessed from the following repositories:https://github.com/kkekkonen/mattermost-server
branch: 5.1-rethreadinghttps://github.com/kkekkonen/mattermost-webapp
branch: 5.1-rethreadinghttps://github.com/kkekkonen/mattermost-redux
branch: mattermost-redux-rethreading -
That's interesting Kaarlo! Is it built-in a Mattermost fork or implemented via a plugin?
-
Kaarlo Kekkonen
commented
My organization wanted this feature (though in this case the user does the rethreading) and had me develop it. It is functional but remains untested in production environment.