feedback
Manage User Feedback
Commands
Section titled “Commands”sentry feedback list [<org/project>]
Section titled “sentry feedback list [<org/project>]”List and search User Feedback
Arguments:
| Argument | Description |
|---|---|
[<org/project>] |
<org>/ (all projects), <org>/<project>, or <project> (search) |
Options:
| Option | Description |
|---|---|
--status <status> |
Mailbox: unresolved, resolved, spam, or all (default: "unresolved") |
-n, --limit <limit> |
Number of feedback items (1-1000) (default: "25") |
-q, --query <query> |
Search query (Sentry issue search syntax) |
-t, --period <period> |
Time range: "7d", "2024-01-01..2024-02-01", ">=2024-01-01" (default: "14d") |
-f, --fresh |
Bypass cache, re-detect projects, and fetch fresh data |
-c, --cursor <cursor> |
Navigate pages: "next", "prev", "first" (or raw cursor string) |
Examples:
# List Feedback (organization auto-detected)sentry feedback list
# List Feedback for one projectsentry feedback list my-org/frontend
# List Feedback across every project in an organizationsentry feedback list my-org/
# Search for a project across accessible organizationssentry feedback list frontend
# Show resolved Feedbacksentry feedback list my-org/frontend --status resolved
# Show the spam mailboxsentry feedback list my-org/frontend --status spam
# Show every status over the last 90 dayssentry feedback list my-org/frontend --status all --period 90d
# Search Feedback messagessentry feedback list my-org/frontend --query "message:*checkout*"sentry feedback view <feedback>
Section titled “sentry feedback view <feedback>”View a User Feedback item
Arguments:
| Argument | Description |
|---|---|
<feedback> |
Feedback: @latest, numeric ID, short ID, <org>/SHORT-ID, or <org>/<project>/<suffix> |
Options:
| Option | Description |
|---|---|
-w, --web |
Open in browser |
-f, --fresh |
Bypass cache, re-detect projects, and fetch fresh data |
Examples:
# View the most recent unresolved Feedbacksentry feedback view @latest
# Most recent unresolved Feedback in an explicit organizationsentry feedback view my-org/@latest
# View by short IDsentry feedback view FRONTEND-2SDJ
# View by numeric IDsentry feedback view 5146636313
# View in an explicit organizationsentry feedback view my-org/FRONTEND-2SDJ
# `view` is the default commandsentry feedback my-org/FRONTEND-2SDJ
# Open the Feedback item in Sentrysentry feedback view my-org/FRONTEND-2SDJ --websentry feedback resolve <feedback>
Section titled “sentry feedback resolve <feedback>”Mark User Feedback as resolved
Arguments:
| Argument | Description |
|---|---|
<feedback> |
Feedback: @latest, numeric ID, short ID, <org>/SHORT-ID, or <org>/<project>/<suffix> |
Examples:
# Resolve a Feedback item (organization auto-detected)sentry feedback resolve FRONTEND-2SDJ
# Resolve a Feedback item in an explicit organizationsentry feedback resolve my-org/FRONTEND-2SDJ
# Resolve the most recently active unresolved Feedbacksentry feedback resolve my-org/@latest
# Return selected fields from the updated Feedbacksentry feedback resolve my-org/FRONTEND-2SDJ --json --fields id,shortId,statussentry feedback unresolve <feedback>
Section titled “sentry feedback unresolve <feedback>”Return User Feedback to the inbox
Arguments:
| Argument | Description |
|---|---|
<feedback> |
Feedback: @latest, numeric ID, short ID, <org>/SHORT-ID, or <org>/<project>/<suffix> |
Examples:
# Reopen a Feedback item, or return it from spam to the inboxsentry feedback unresolve FRONTEND-2SDJ
# Reopen by numeric IDsentry feedback unresolve 5146636313
# `reopen` is an alias for `unresolve`sentry feedback reopen FRONTEND-2SDJ
# Specify an organization explicitlysentry feedback unresolve my-org/FRONTEND-2SDJ
# Return selected fields from the updated Feedbacksentry feedback unresolve FRONTEND-2SDJ --json --fields id,shortId,statussentry feedback spam <feedback>
Section titled “sentry feedback spam <feedback>”Mark User Feedback as spam
Arguments:
| Argument | Description |
|---|---|
<feedback> |
Feedback: @latest, numeric ID, short ID, <org>/SHORT-ID, or <org>/<project>/<suffix> |
Examples:
# Move a Feedback item to the spam mailboxsentry feedback spam FRONTEND-2SDJ
# Mark as spam by numeric IDsentry feedback spam 5146636313
# Specify an organization explicitlysentry feedback spam my-org/FRONTEND-2SDJ
# Return selected fields from the updated Feedbacksentry feedback spam FRONTEND-2SDJ --json --fields id,shortId,statusAll commands support --json for machine-readable output and --fields to select specific JSON fields.
Feedback issues
Section titled “Feedback issues”Modern User Feedback is stored as Feedback issues. sentry feedback list
always limits issue searches to issue.category:feedback; it does not use the
legacy User Reports API.
The unresolved inbox from the last 14 days is shown by default. Use --status
to select another mailbox (resolved, spam, or all) and --period to
expand the time range. Use --json for the standard paginated envelope.
Navigate pages in either direction with --cursor next and --cursor prev.
Viewing Feedback
Section titled “Viewing Feedback”@latest selects the most recently active unresolved Feedback. view is the
default command, and show is an alias.
The detail view includes the complete message and, when available, its latest
event, linked error, Session Replays, and attachment metadata. If the supplied
ID belongs to another issue category, use sentry issue view instead.
Updating Feedback
Section titled “Updating Feedback”resolve accepts the same IDs and URLs as view and reads the current state
before selecting a Feedback item. It rejects other issue categories before
making changes. JSON output contains the updated Feedback issue from Sentry.
unresolve (alias reopen) marks Feedback as unresolved, reopening resolved
Feedback or returning spam to the inbox. It uses the same identifier resolution
and category check as resolve. Other issue categories are rejected before
making changes. JSON output contains the updated Feedback issue from Sentry.
spam checks that the target is Feedback before updating it. Sentry stores spam
with status ignored, which is also the value returned in JSON output. Use
unresolve to return it to the inbox; this sets the status to unresolved
regardless of its status before being marked as spam.