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

Suspended abilities leave no mod-visible history #748

Open
cellio opened this issue Dec 30, 2021 · 1 comment
Open

Suspended abilities leave no mod-visible history #748

cellio opened this issue Dec 30, 2021 · 1 comment
Labels
area: backend Changes to server-side code complexity: average Not particularly hard, not particularly trivial. priority: high type: change request New feature or request

Comments

@cellio
Copy link
Member

cellio commented Dec 30, 2021

When a moderator suspends an ability, the user receives an inbox notification (with a customizable message from the moderator) and the ability shows as suspended on the mod "privileges" page. However, there's no other record, which poses two problems:

  1. Other moderators can't see the message that was sent to the user.
  2. After the suspension expires, the fact that it ever happened is not visible. If the problem recurs, moderators can't review the history.

Let's record ability suspensions, at least, as annotations. Perhaps they should also be recorded in full user activity, because suspensions are.

@cellio cellio added area: backend Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: high type: change request New feature or request labels Dec 30, 2021
@luap42 luap42 added complexity: average Not particularly hard, not particularly trivial. and removed complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Dec 30, 2021
@luap42
Copy link
Member

luap42 commented Dec 30, 2021

As far as I can tell, the effort required for this issue should be quite low. However some design considerations and some fuzzying might need to be done, hence I'm marking this as average complexity, although it most definitely is on the lower end of averagely complex issues... ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Changes to server-side code complexity: average Not particularly hard, not particularly trivial. priority: high type: change request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants