Add top-level `sentry feedback` commands for managing User Feedback

Open
#1,262 0 comments 0 reactions 1 assignee View on GitHub

@betegon is already working on this.

Since Jul 17, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

Summary

Add a top-level sentry feedback command group to inspect and manage User Feedback for a Sentry organization, similar to sentry issue.

This is separate from the existing sentry cli feedback command, which submits feedback about the CLI itself.

Modern User Feedback is backed by issues. The implementation should use the organization Issues API with a mandatory issue.category:feedback filter, not the legacy User Reports endpoints.

Command roadmap

First PR
  • sentry feedback list [<org>/<project>] — list and search feedback with pagination and unresolved/resolved/spam mailboxes
  • sentry feedback view [<org>/<project>/]<feedback-id> — show the feedback issue plus its latest event context; make view the default and expose the standard show alias
Follow-ups
  • sentry feedback resolve <feedback-id>
  • sentry feedback unresolve <feedback-id> (reopen alias)
  • sentry feedback spam <feedback-id>
  • sentry feedback unspam <feedback-id> (restore alias)
  • sentry feedback mark-read <feedback-id>
  • sentry feedback mark-unread <feedback-id>
  • sentry feedback assign <feedback-id> <user-or-team>
  • sentry feedback unassign <feedback-id>
  • sentry feedback comment <feedback-id> — add an internal comment; editing/deleting comments can follow
  • sentry feedback delete <feedback-id>
  • sentry feedback summary [<org>/<project>] — AI summary when available
  • sentry feedback categories [<org>/<project>] — AI-generated categories when available

The first implementation PR should only cover list and view; this issue tracks the full command group.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.