Summary
When an agent is inspecting a specific error event, there is no way to find User Feedback submissions linked to that event via the MCP. Going from feedback → error works today via get_sentry_resource, but the reverse path is not supported.
Current behavior
search_issues with issue.category:feedback lists feedback submissions but provides no filter to scope results to a specific linked error event ID. The feedback issue model returned by the API also does not surface the linked event ID in its metadata (fixture reference).
Gap
Agents and users who start from an error event cannot reliably find associated User Feedback. The only workaround is a fuzzy heuristic: match by affected user + time window, which is imprecise and not always possible.
Options
- Add a
linked_event search filter to search_issues (e.g. issue.category:feedback linked_event:EVENT_ID) if the Sentry issues API supports it
- Expose the linked event ID in feedback issue metadata returned by
get_issue_details / get_sentry_resource, enabling client-side correlation
- Document the intended triage path if a supported filter already exists upstream
Context
Reported by a customer using the User Feedback widget to collect user bug reports. Users submit feedback linked to specific error events; their coding agent needs to navigate from an error to its associated feedback submissions for triage.
Summary
When an agent is inspecting a specific error event, there is no way to find User Feedback submissions linked to that event via the MCP. Going from feedback → error works today via
get_sentry_resource, but the reverse path is not supported.Current behavior
search_issueswithissue.category:feedbacklists feedback submissions but provides no filter to scope results to a specific linked error event ID. The feedback issue model returned by the API also does not surface the linked event ID in its metadata (fixture reference).Gap
Agents and users who start from an error event cannot reliably find associated User Feedback. The only workaround is a fuzzy heuristic: match by affected user + time window, which is imprecise and not always possible.
Options
linked_eventsearch filter tosearch_issues(e.g.issue.category:feedback linked_event:EVENT_ID) if the Sentry issues API supports itget_issue_details/get_sentry_resource, enabling client-side correlationContext
Reported by a customer using the User Feedback widget to collect user bug reports. Users submit feedback linked to specific error events; their coding agent needs to navigate from an error to its associated feedback submissions for triage.