User Feedback

Read-only inbox of player-submitted user feedback. The first subjects are resolved in-game and Match question answers. Players file reports from Live (Report this on Recent answers) or a mobile client. Operators can file the same report from History while reviewing a player. This inbox page does not write.

URL	/admin/user-feedback
REST	GET /api/user-feedback/form · GET /api/user-feedback · GET /api/users?q= · GET /api/matches

Player how-to (form contract and POST): Report this.

Workflow

1. Open Manage → User Feedback (/admin/user-feedback), or follow Feedback on a match (that deep-link sets match_id and shows all submitted days for the match).
2. Filter by Submitted local day (when the feedback was created — not the match’s scheduled day). Optionally search a player (email, name, or user id) and/or pick a match (league + scheduled day). Subject and topic filters come from the form catalog.
3. Read topic + description. Expand a row for selected choice, correctness, resolution reason, and ids. Follow History or Issuance Explorer when the deep-link is present.

Filters are independent and optional. Clearing them returns the inbox to today’s submitted day with no player or match.

Columns

Column	Meaning
Submitted	Local time of created_at (UTC on the API)
User	Submitter display name
Subject	Form catalog label (in-game question or Match question)
Match	Label and shortcode when the subject has a match. The label links to that match
Question	Question text from the parent issuance. For question subjects this links to Issuance Explorer for that issuance
Topic	Catalog topic (incorrect resolution, question issued incorrectly, other)
Description	Optional player note (max 250 characters)

Notes

• One feedback row per player + subject. Duplicate POSTs return 409.
• Admin list pagination: feedback is the page; feedback_count is the filtered total.
• An operator Report this from History is stored against the answer owner (same unique key as a player submission).