Appearance
Feedback
The Feedback page collects submissions sent through the in-app feedback widget. Staff and instructors can report a bug, suggest something, or flag a problem without leaving the app, and those reports land here for triage.
Used by: Admin and Super Admin.
Where feedback comes from
The feedback widget appears in the Admin and in the Portal. In the Portal it only shows for people signed in with a staff or instructor account (Admin, Super Admin, or Instructor). Regular members do not see it, so member questions still need to come in through your usual email or phone channels. When someone submits, the system captures:
- Category — Bug, UX / Usability, Performance, Missing Feature, Data Sync, or General.
- Page URL — the exact page they were on when they submitted.
- Description — what they wrote.
- Screenshot — optional, if they attached one.
- Server log at time of submission — technical details attached automatically to help diagnose bugs, such as who submitted, which page, whether a screenshot was attached, and which browser they used.
- Submitter — their name and email when available.
If a submission is rejected (for example because the person's session had expired), the widget now shows the actual reason instead of a generic error, and keeps what they typed so they can try again.
Reviewing submissions
- Go to https://admin.uibeta.org/admin/feedback.
- Submissions are grouped by status: New, Reviewed, and Fixed. New items are at the top so nothing gets lost. The Fixed group starts collapsed; click its header to open it. The page remembers which groups you opened or closed.
- Click a row to open the detail view with the full description, page URL, screenshot, and server log.
- If a screenshot is attached, you can download it from the detail view.
When the list is incomplete
The page loads up to the 500 most recent submissions. Above the list you will see either "Showing all N submissions" or, once there are more than 500, a yellow warning: "Showing the 500 most recent submissions — this list is incomplete." When that warning appears, older submissions exist but are not shown. Ask Andrew before treating the page as the full history.
Marking status
From the detail view you can move a submission through its lifecycle:
- Mark as Reviewed — you have seen it and triaged it.
- Mark as Fixed — the underlying issue is resolved.
Status is just for staff tracking. Changing it does not email the submitter.
Creating a GitHub issue
For anything that needs a developer, use Create Issue from a submission. This opens an issue in the project's GitHub repository pre-filled from the feedback, and links the issue number and URL back onto the feedback record so you can follow it. Use this for real bugs and feature requests rather than pasting details by hand.
Need help? Contact Andrew.