Reviewing Feedback

The Feedback system allows team members to submit suggestions, report issues, and request features. This guide covers how to review and respond to feedback.

Accessing Feedback

1. Navigate to Admin in the sidebar.
2. Click on Feedback.
3. The feedback queue displays all submissions.

Feedback Queue

The feedback list shows:

Column	Description
Date	When the feedback was submitted
From	Member who submitted (or anonymous)
Type	Bug Report, Feature Request, General
Status	New, In Review, Resolved, Closed
Preview	First line of the feedback content

Feedback Types

Type	Purpose
Bug Report	Something isn’t working correctly
Feature Request	Suggestion for new functionality
General	Other feedback, questions, or comments

Reviewing a Submission

1. Click on a feedback item to open it.
2. Review the full content and any attachments.
3. Update the status as you work on it.
4. Add internal notes (visible only to admins).
5. Optionally respond to the member.

Status Workflow

Status	Meaning
New	Unread, requires review
In Review	Being investigated or considered
Resolved	Issue fixed or request implemented
Closed	No action taken (duplicate, out of scope, etc.)

Responding to Feedback

To reply to the member:

1. Open the feedback item.
2. Enter your response in the reply field.
3. Click Send Response.

The member receives a notification with your response.

Internal Notes

Add private notes for other admins:

1. Open the feedback item.
2. Use the Internal Notes section.
3. These notes are never visible to the submitter.

Use internal notes to:

• Document investigation steps
• Link to related issues
• Note decisions and rationale

Filtering and Sorting

Use the filter controls to:

• Filter by Status — Show only New, In Review, etc.
• Filter by Type — Show only Bug Reports, etc.
• Sort by Date — Newest or oldest first

Best Practices

Response Time

• Acknowledge Quickly — Even a brief “thanks, we’re looking into it” helps.
• Set Expectations — Let members know realistic timelines.
• Follow Up — Update members when their issue is resolved.

Prioritization

• Safety Issues First — Anything affecting team safety takes priority.
• High Impact — Issues affecting many users.
• Quick Wins — Easy fixes that improve experience.

Documentation

• Track Patterns — Multiple reports of the same issue indicate priority.
• Link to Development — If using external issue trackers, reference them.
• Archive Don’t Delete — Keep feedback history for reference.

Anonymous Feedback

If anonymous feedback is enabled:

• Members can submit without identifying themselves.
• The “From” field shows “Anonymous.”
• You cannot directly respond (no reply option).
• Consider the feedback on its merits, not the source.

See Also

• Admin Panel Overview — Other admin functions.