Allow specifying reasons when closing topics in workflows

AI-generated summary

In the ‘Feature’ category under ‘workflows’, KockaAdmiralac proposes adding the ability to specify a reason when closing topics via workflow actions. The user describes a scenario where a workflow button allows the original poster to close their topic, but since regular users lack the necessary permissions, the action is performed by the system user. This results in confusion because the topic closes without any indication of why. The author notes that while topic closing supports attached reasons, the Topic > Close topic node in workflows currently lacks the functionality to define them, requesting an update to support this specification.

I have a workflow that adds a button to topics, allowing the original poster to close the topic. Since regular users don’t have the permission to close topics, I have to perform this action as the system user. This looks confusing, because a topic is suddenly closed by a system user with no indication of why that is.

It would help me if the Topic > Close topic node allowed specifying a reason for closing the topic. It seems possible for topic closing to have a reason attached to it but workflows don’t currently seem to support specifying this reason.

1 Like