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

Account / User profile: Reporting entries should notify more editors/users #1857

Open
andreoda opened this issue Dec 4, 2024 · 3 comments
Open
Labels
complexity: unknown Unknown days of work content: messages DMs (direct messages), PMs (private messages), notifications content: users Users (account/profile), user settings entry-activity Entry activities/changes to entries, Entry reports feature request moderation Moderator or trusted user actions/tasks priority: high Issues/Tasks that should be done ASAP

Comments

@andreoda
Copy link
Member

andreoda commented Dec 4, 2024

When reporting an entry, and no specific revision is selected, only the last editor gets notified (messaged) (as far as I know). I think it is better if the creator of the entry + the last editor OR the creator + the last 3 editors should get notified, even when no revision is selected.

@andreoda andreoda added moderation Moderator or trusted user actions/tasks content: users Users (account/profile), user settings priority: high Issues/Tasks that should be done ASAP entry-activity Entry activities/changes to entries, Entry reports content: messages DMs (direct messages), PMs (private messages), notifications complexity: unknown Unknown days of work feature request labels Dec 4, 2024
@mn7216
Copy link
Contributor

mn7216 commented Dec 8, 2024

I think forcing selection of a revision (or revisions) may be better

@andreoda
Copy link
Member Author

andreoda commented Dec 8, 2024

@mn7216
good idea

@andreoda
Copy link
Member Author

andreoda commented Jan 3, 2025

Besides these two initial ideas, a better solution by Finn (Pyther) that also combines other ideas mentioned in the report page overhaul:

Make the "Report an error" dialog a two step process:

Example:

  • Broken PV: Require user to choose a specific PV from a list
  • Invalid/Missing information: Require information regarding which fields are wrong (as toggles, like the artist role menu)
  • Inappropriate content: Notes required
  • Other: Notes required
  • Invalid tag usage: Require user to choose which tags are invalid

Example:

If you notice that the titles are wrong:

  • you click directly on "Report an error"
  • choose "Invalid information" and "song name"
    -> system gets the last edit which changed the song names and notifies that users

instead of:

  • Going into "View modifications"
  • Going to the last edit which changed the song title
  • Clicking on "Report an error" on that specific version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: unknown Unknown days of work content: messages DMs (direct messages), PMs (private messages), notifications content: users Users (account/profile), user settings entry-activity Entry activities/changes to entries, Entry reports feature request moderation Moderator or trusted user actions/tasks priority: high Issues/Tasks that should be done ASAP
Projects
Development

No branches or pull requests

2 participants