You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2021. It is now read-only.
📢 Suggestion proposed by DanNick | Daniel (158672265083355147)
What is the title of your suggestion?
setting to send ticket send confirmation via dm
Explain your suggestion more accurately (It's best to give as much information as possible, so that we can implement the suggestion better)
There should be a setting whether the bot's answer after creating a ticket should be sent in the channel (as it works currently) or via dm to the ticket creator
Why should we add this feature?
a bit more privacy since users maybe don't want others to know that they created a ticket (maybe due to a private problem)
Comments:
📝 DanNick | Daniel: The command deletion setting should also be overwritten so that the command always gets deleted (otherwise you can see the content of the ticket)
❗✅ Dadi: very good idea - important
The text was updated successfully, but these errors were encountered:
📢 Suggestion proposed by DanNick | Daniel (158672265083355147)
What is the title of your suggestion?
setting to send ticket send confirmation via dm
Explain your suggestion more accurately (It's best to give as much information as possible, so that we can implement the suggestion better)
There should be a setting whether the bot's answer after creating a ticket should be sent in the channel (as it works currently) or via dm to the ticket creator
Why should we add this feature?
a bit more privacy since users maybe don't want others to know that they created a ticket (maybe due to a private problem)
Comments:
📝 DanNick | Daniel: The command deletion setting should also be overwritten so that the command always gets deleted (otherwise you can see the content of the ticket)
❗✅ Dadi: very good idea - important
The text was updated successfully, but these errors were encountered: