Option to disable bot notification message? about mattermost-plugin-wrangler

[gabrieljackson]

This is a very interesting use case and I can definitely add this option to wrangler. While the majority of messages being moved benefit from the context of the bot post, I can see how that wouldn't be the case for this scenario.

I am thinking that this sort of option would be set in the plugin configuration and would apply to all actions taken by wrangler. Would this work for you?

[alexanderlhk]

Hey @gabrieljackson, thanks for the prompt response and the amazing contribution so far to this plugin.

I think leaving an option for the user to disable EITHER/BOTH the notifications that is found in the original thread and the receiving channel would be great.

This will help, in our case, to reduce the time spent deleting the bot messages to reduce the mess/confusion of the flow of the messages/conversation (as you know, Mattermost does not give us the option to bulk delete messages... yet).

[gabrieljackson]

Sorry about that temporary close+open on the issue. I got a bit too click happy on the comment box.

I was wondering if this behavior is something that you would want in the wrangler command and the webapp UI, or if the command would suffice? It sort of sounds like you may have some automation in place for this use-case, but I wasn't sure. Due to there being a few messages that wrangler will make depending on the action being taken, I am trying to decide if exposing this in the UI would be worth the possible confusion it may bring. Any input on this would be appreciated.

[gabrieljackson]

@alexanderlhk, I have added a silent flag to the /wrangler move thread command. This silences all Wrangler messages when moving threads which should cover the behavior you are looking for. This will be included in the next wrangler release.

I am thinking I will keep this functionality in the command line only for now. I will probably add it to the UI as well in the future once I decide on a good way to ensure users are fully aware of how it impacts the thread move experience. Is the command line flag helpful to you or do you solely use the Wrangler UI to move messages?

[alexanderlhk]

Hey Gabriel, Yeah. I think this is what I was looking for. I think command line is a good solution for now Thank you. I look forward to your favourable reply. Regards, Alexander L.

[jomaxro]

Hey @gabrieljackson,

Just started using this plugin. Our team doesn't make use of threads much, so when a "conversation" needs to be moved, we end up moving a bunch of individual posts. That means a bunch of wrangler bot posts in 2 channels.

It looks like the silent flag hasn't made it into a release, is that correct? Any timeline for doing so.

Also, we tend to use the UI option, as it's much quicker than finding post and channel IDs. If support for silent moves could be added to the UI, we'd be quite appreciative. A plugin setting that applies to all wrangler move/copy actions would cover our use case, though I can see others preferring it on a post-by-post basis.

[gabrieljackson]

@jomaxro you are right that the silent flag had not quite made it into the last published release. I will be fixing this soon with a new release with some additional features.

As you can see, I just merged a change to expose the silent flag via the webapp as requested.

A plugin setting that applies to all wrangler move/copy actions would cover our use case, though I can see others preferring it on a post-by-post basis.

For now, the option in the webapp will be exposed to users in the move thread modal via a checkbox. The good news is the state of the checkbox will be saved if you want to move a bunch of messages in a row meaning you won't have to enable or disable it each time. I will consider adding a plugin-wide option in the future, but this should work for now.