Skip to content

Mod audit doens't log who issued moderation command #280

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

Closed
marko-radosavljevic opened this issue Nov 24, 2021 · 4 comments
Closed

Mod audit doens't log who issued moderation command #280

marko-radosavljevic opened this issue Nov 24, 2021 · 4 comments
Labels
enhance command Modify or improve an existing command or group of commands of the bot priority: normal valid This issue/PR is validated and ready to be picked. This auto adds items to TJ project board.

Comments

@marko-radosavljevic
Copy link
Contributor

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

After using moderation commands of our bot, audit doesn't log who issued the command.
image

Describe the solution you'd like

image
Or some other way to indicate who issued the command. ☺️

@marko-radosavljevic marko-radosavljevic added enhancement New feature or request good first issue Good for newcomers priority: normal labels Nov 24, 2021
@marko-radosavljevic marko-radosavljevic added enhance command Modify or improve an existing command or group of commands of the bot and removed enhancement New feature or request labels Nov 24, 2021
@Zabuzard
Copy link
Member

Note that this is only "easy" to do if it came from our own bot actually. Right now we read the information from the audit log, but Discords audit log has no additional information.

So the way I see this feature being implemented is:

  • have a database table that lists all sanctions done with our bot, with timestamp (will likely be introduced by a /audit command anyways (not sure if we have a GH issue for that already))
  • lookup the ban in the audit log with the timestamp in that table (probably have to give it some variance of +-5 seconds or similar to find a match)
  • decorate the message written to the channel with the information gathered from the database

@Zabuzard Zabuzard added the blocked This issue is currently blocked by another issue (see comments) label Dec 3, 2021
@Zabuzard
Copy link
Member

Zabuzard commented Dec 3, 2021

Blocked by the missing audit database table, which also blocks the work on temporary bans and the mute command right now.

@Zabuzard Zabuzard removed the good first issue Good for newcomers label Dec 3, 2021
@Zabuzard
Copy link
Member

Zabuzard commented Dec 3, 2021

Created an issue for it, blocked by #297

@Zabuzard Zabuzard removed the blocked This issue is currently blocked by another issue (see comments) label Dec 10, 2021
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added stale inactivity-closed Issues that have been closed due to inactivity, but are otherwise valid and might be reopened later labels Jan 10, 2022
@Zabuzard Zabuzard removed the stale label Jan 17, 2022
@marko-radosavljevic marko-radosavljevic added valid This issue/PR is validated and ready to be picked. This auto adds items to TJ project board. and removed inactivity-closed Issues that have been closed due to inactivity, but are otherwise valid and might be reopened later labels Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhance command Modify or improve an existing command or group of commands of the bot priority: normal valid This issue/PR is validated and ready to be picked. This auto adds items to TJ project board.
Projects
None yet
Development

No branches or pull requests

2 participants