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

Mod tools: unify user annotations and warnings/suspensions pages? #749

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

Mod tools: unify user annotations and warnings/suspensions pages? #749

cellio opened this issue Dec 30, 2021 · 1 comment
Labels
area: backend Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: change request New feature or request

Comments

@cellio
Copy link
Member

cellio commented Dec 30, 2021

Currently, for a user, mods can see a list of annotations (where they can add new ones), and separately a list of warnings sent to the user (including suspensions). #748 asks that ability suspensions be added here.

Moderators reviewing a user's activity, particularly when problematic behavior is ongoing or recurring, need to be able to see all the history easily. We're relying on them to know/remember to check a couple different places. I think I understand why those pages are different (the content is tables with different columns), but it would be better if we could either unify them or build a "mod user summary" view on top of them.

As a mod, I want to see a reverse-chronological list of all things that either involved messages to the user (warnings or ability suspensions, currently) or were noteworthy enough for a moderator to write an internal note (annotations). A list with links is fine; it's ok to have to follow a link for the details. But seeing something all together in one place is pretty important for mods.

Example of what I mean:

Annotation Summary: Ploni Almoni

  • 3d ago: suspension, 30 days: rudeness (Mod999)
  • 3d ago: annotation: returned from suspension and repeated personal attacks in comments (Mod999)
  • 11d ago: suspension, 7 days: rudeness (Mod613)
  • 12d ago: warning: rudeness (Mod999)
  • 13d ago: annotation: deleted several rude comments (Mod613)
  • 21d ago: ability suspension: participate everywhere (Mod613)
  • 1m ago: warning: many closed questions (Mod999)

Each of the items in that list ("suspension...", "annotation...", etc) would be links to the detailed info. I don't care if those links are to the table entries in the existing pages or to standalone pages -- whatever's easier. The summary would record who took the actions (Mod613 and Mod999 in my examples). As with all our relative times, the timestamps would be available in tooltips.

The mod tools page for a user is currently a list of links plus some "definitely use with care" buttons. We could add this summary to that page instead of creating yet another page under the links. Over time we'll probably want to build that page out more, but this is a good start.

In addition to this being where the "all tools" button takes you, if there are any annotations or warnings, we should indicate that somehow on the profile page for mods only. One way to do that would be to add "N annotations" to the link text for the "mod tools" button, but there are probably better ways.

@cellio cellio added area: backend Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: change request New feature or request labels Dec 30, 2021
@cellio
Copy link
Member Author

cellio commented May 18, 2022

Related work on #767.

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: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: change request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant