QA • QA • QA • QA • QA • QA • QA • QA • QA • QA • QA • QA • QA • QA • QA

Feedback

Feedback is retired. It no longer accepts new reports — Issues superseded it. To report a bug, request a feature, or ask a question, use the help button's Create issue action or go to /Issues. What remains here is the historical archive and its admin triage screens.

What this section is for

Feedback was the original in-app way to report a bug, suggest an improvement, or ask a question. Reports already filed are kept — with their categories, screenshots, page URLs, and conversation threads — so admins can finish triaging them. Nothing new can be filed.

Status still moves from Open to Acknowledged, then to Resolved or Won't Fix, and a report can still be linked to a GitHub issue.

Key pages at a glance

Both require the Admin role. There is no reporter-facing view — a report's own author cannot open it.

  • Feedback queue (/Feedback) — every historical report, with the selected report's detail panel beside it
  • Feedback detail (/Feedback/{id}) — the full report: description, screenshot, page URL, status, assignment, and the conversation thread. It is a panel inside the queue, not a page of its own; opening the URL directly sends you to /Feedback?selected={id}

As a Volunteer

Nothing. You cannot file feedback and you cannot open your old reports. File an issue instead — the help button on any page, Create issue, or /Issues.

If an admin replies to one of your historical reports you still get an email with their response in your preferred language, and a notification in your inbox telling you a response arrived. Neither links back to the report, because the report is admin-only now; the reply text is in the email itself.

Automation

/api/backdoor/feedback is key-authenticated (X-Api-Key), with the personal key an admin allocated to you at /Backdoor. It covers the same triage the UI does — list reports, read one and its messages, post a message, and change status, assignment, or the linked GitHub issue — but it has no report-creation endpoint. A message posted through it is an admin reply, exactly as one posted in the UI.

  • Admin — roles are assigned via the admin role pages; API keys are allocated at /Backdoor