Feedback & Issues
How Staff Submit Feedback
Use the Send Feedback button in the portal header to report a problem or suggest an improvement.
Choose the option that best matches the request:
- Report Issue — use for bugs, broken workflows, missing data, or confusing behavior.
- Suggest Feature — use for improvements or new workflow ideas.
- General Feedback — use only when it is not clearly a bug or feature request.
The form is structured so admins can triage feedback without guessing. Include the page/module, what you expected, what actually happened, and any non-sensitive reference that helps reproduce the issue.
Do not include sensitive data
Do not paste passwords, tokens, private client documents, bank details, government IDs, or confidential client information into feedback. If an issue involves sensitive data, describe the category of data and ask an admin how to share evidence safely.
When feedback is submitted, it is logged in the system and visible to admins for triage.
Viewing Submitted Feedback (Admin)
Admins can view feedback from Admin → Feedback in the sidebar.
The feedback table is sorted by newest first and shows:
- Type — bug/report issue, feature request, or other feedback.
- User and device — who submitted it and the browser/device context.
- Page — the page/module where it was submitted.
- Status — current triage state.
- Date — when it was submitted.
Click a row to open the detail panel. For structured submissions, the detail panel shows:
- Environment, such as production or staging.
- Severity / work impact.
- Expected behavior.
- Actual behavior or current gap.
- Page URL and screen size.
- Admin notes.
Feedback Status Workflow
| Status | What It Means |
|---|---|
| New | Just submitted and not yet reviewed. |
| Acknowledged | Admin has reviewed it but work has not started. |
| In Progress | A fix, decision, or implementation path is actively being worked. |
| Resolved | Verified fixed or implemented in the target environment. |
| Dismissed | Not actionable, duplicate, obsolete, or intentionally not prioritized. |
Do not mark feedback as resolved only because a related change exists. Mark it resolved only when the behavior is verified in the relevant environment, or when an approved release/verification note says it is safe to close.
Admin Actions
As an admin, you can:
- Update status — move feedback through the triage workflow.
- Add internal notes — record evidence, Linear issue links, verification notes, or why an item was dismissed.
- Filter by type/status — focus on new items, unresolved issues, or historical resolved feedback.
- Map feedback to Linear — create or link an issue when the item needs engineering or product follow-up.
The feedback page does not send a direct reply to the submitter. If follow-up is needed, contact the submitter through the normal internal channel and record the summary in admin notes.
Production vs Staging Guidance
- Production feedback is live operational evidence. Do not bulk-close or rewrite it without explicit approval and verification.
- Staging feedback is safe for QA smoke tests and release validation, but it should not be treated as proof that production users saw a fix.
- If a feedback item is sensitive, stop and use a private evidence path instead of copying details into chat or public issue trackers.
Weekly triage
Review the feedback queue weekly. Keep new items low, move actionable work into Linear, and leave evidence before changing status.