Here is my suggestion for a bot template to close an issue, label it as "no-support" and give a feedback to the user.
This is for closing issues that are support requests rather than being a bug report. This is also an import template, because this affects large amounts of issues.
One has to be careful though, because there is a fine line between an issue being a bug report that needs more feedback by the reporter or some joint debugging or an issue that is just a support request where there is no actual bug. This has to be evaluated on a case-by-case basis. The template shall try to reflect this.
Cheers
Thomas
Hi [REPORTER USERNAME]
I am closing this issue because we think there is no actual bug in Rocket.Chat in what you're describing. Here's why:
[FREE TEXT]
We use Github mainly for discussing bugs though. We understand, that setting up and operating a Rocket.Chat server is not trivial, yet we do not have the woman/man-power to help everybody. That is unfortunate, but simply a limitation of time. If it should turn out from your feedback to this message, that there is a bug involved, we will try to fix it with you.
That being said, we are very thankful that our community also does a great job in helping each other. I would therefore like to point you to some places where you can try asking for help. Usually, some friendly human being has time for you and your issue:
If you don't find a solution to your problem there, don't fret, as we also offer paid support: https://rocket.chat/support
You could, of course, spare yourself the hassle entirely and just choose the hosted version, where we provide you with a running Rocket.Chat instance: https://rocket.chat/cloud
[GENERIC ROCKET.CHAT SALUTATION]
[USERNAME OF THE ONE WHO TRIGGERED THE BOT]
Usage:
@rocket-cat nosupport+close [REPORTER USERNAME] [FREE TEXT]
Here is my suggestion for a bot template to close an issue, label it as "no-support" and give a feedback to the user.
This is for closing issues that are support requests rather than being a bug report. This is also an import template, because this affects large amounts of issues.
One has to be careful though, because there is a fine line between an issue being a bug report that needs more feedback by the reporter or some joint debugging or an issue that is just a support request where there is no actual bug. This has to be evaluated on a case-by-case basis. The template shall try to reflect this.
Cheers Thomas