Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edit old bot behavior to incorporate join/left logs from all server, indicating the server name to avoid confusion. #3187

Closed
2 tasks
grifgrif opened this issue Sep 8, 2022 · 3 comments
Assignees
Labels
feature request staged Staged for next version

Comments

@grifgrif
Copy link

grifgrif commented Sep 8, 2022

Is your feature request related to a problem? Please elaborate.

Yes,
A while ago the bot notified the thread when a user left the server, without indicating the server he left, making confusion.
To fix it, the bot behavior is to indicate when the user left the current server. But when doing a Support server different from the main, we don't have this important log.
Having this old message indicating where he left/join would be useful and not confusing as before.

Describe the solution you'd like

When a user with a ticket opened leave/join any server in the bot jurisdiction, the bot will make a log in it, indicating the server name and if he can still talk to the user (making an update if there are a few servers left or if the bot can't reach the user to avoid any redaction of a message that can't be heard.)

Does your solution involve any of the following?

  • Logviewer
  • New config option

Describe alternatives you've considered

No,
The actual behavior is to make this log for the current server.
But the point of such log is not to track the user, but to know if we can contact him. Having the bot react that way is more logical and informative.

Who will this benefit?

Any server who use a different server to receive tickets or any bot who have multiples servers.

Additional Information

No response

@sebkuip
Copy link
Member

sebkuip commented Sep 8, 2022

The bot is not supposed to be in servers that aren’t configured. It even gives a warning when starting that other servers than configured are detected and potential errors might arise.

@grifgrif
Copy link
Author

grifgrif commented Sep 8, 2022

Sure,
We run this bot since years, and we never had an error nor any issues with it.
This is literally the only issue with multiserver capabilities. It would make the bot officially multiserver compatible.

@StephenDaDev
Copy link
Member

While its not officially supposed to be, this is a configuration we have recommended publically for a few instances. Seems like this would be a good thing to implement.

@Taaku18 Taaku18 self-assigned this Jul 11, 2023
@Taaku18 Taaku18 added the staged Staged for next version label Nov 20, 2023
@Taaku18 Taaku18 closed this as completed Nov 26, 2023
khakers pushed a commit to khakers/OpenModmail that referenced this issue Jun 18, 2024
khakers pushed a commit to khakers/OpenModmail that referenced this issue Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request staged Staged for next version
Projects
None yet
Development

No branches or pull requests

4 participants