If I understand your question: No, it won’t “screw anything up” — it’s meant to be safe in that it will never prevent sending a new notification to slack, it’s just that if the integration knows about a thread, it will send it to the thread instead of to the channel. If it’s not aware of a thread context for any reason, then it will send to the channel as configured in the rule.
“All posts with threaded replies” means that:
- When a new post is added to an existing topic:
- If a thread ID has been stored for the topic, use it to post a thread
- If no thread ID has been stored for the topic, after posting the notification to slack, use that new slack post’s thread ID for further posts on the topic. It will start threading from that point on.
- When a new topic is posted to slack, store its resulting thread ID so that additional posts on that topic are sent to slack as threaded responses.
I summarize that as “act just like watch, except if it knows about a thread to post to, do that instead”
Additionally, when using the “transcript” feature to post slack content as a new topic in Discourse, regardless of any rule settings, it always tries to store the thread ID, so that if a thread rule either already exists or is added in the future, post replies on the new topic in discourse are announced on the appropriate slack thread.
I’m sure your existing rules could be changed with some bin/rails c typing but I don’t want to do that to my live site where I’ve intentionally chosen which channels to thread and which not to, and I’m way too new to ruby to type random ruby as help advice on a forum and expect it not to blow up in your face.
Other than it probably starts with DiscourseChat::Rule.where( I’m not going to be much help. Sorry!