---
name: sentry-issue-triage
description: Triage a Sentry project's unresolved issues by ranking them by user impact, grouping likely duplicates, and proposing assign, resolve or ignore for each, with approval before changes. Use when the user asks to clean up, triage or prioritise Sentry issues or reduce Sentry noise.
---

# Triage Sentry issues

## Steps

1. Resolve the project with `find_projects`. List the backlog with `find_issues`, for example `is:unresolved is:unassigned`, sorted by users affected.
2. Skim each of the top issues with `get_issue_details`, enough to tell a real bug from noise such as browser extensions, bots, or network errors the user cannot act on.
3. Group issues that share a culprit or message pattern; they are often one bug.
4. Propose one action per issue:
   - Assign, to a team from `find_teams` or a person, when ownership is clear.
   - Resolve in the next release, when the fix already shipped.
   - Ignore until it escalates, for known noise, with the reason.
   - Investigate, for real impact with an unknown cause.
5. Suggest inbound filters or a fix to the SDK configuration for repeated noise, with `search_docs` for the setting.

## Apply

Show the table: issue, users, events, proposed action and reason. Make only the approved changes with `update_issue`, and wait for the user's yes before touching any issue.