issue

Track and manage Sentry issues.

Commands

sentry issue list

List issues in a project.

sentry issue list --org <org-slug> --project <project-slug>

Options:

Option	Description
--org <org-slug>	Organization slug (required)
--project <project-slug>	Project slug (required)
--query <query>	Search query
--status <status>	Filter by status (unresolved, resolved, ignored)
--limit <n>	Maximum number of issues to return
--json	Output as JSON

Example:

sentry issue list --org my-org --project frontend

ID            SHORT ID    TITLE                           COUNT   USERS
123456789     FRONT-ABC   TypeError: Cannot read prop...  1.2k    234
987654321     FRONT-DEF   ReferenceError: x is not de...  456     89

With search query:

sentry issue list --org my-org --project frontend --query "TypeError"

sentry issue view

View details of a specific issue.

# By issue ID
sentry issue view <issue-id>

# By short ID
sentry issue view <short-id>

Arguments:

Argument	Description
<issue-id>	The issue ID (numeric) or short ID (e.g., PROJ-ABC)

Options:

Option	Description
-w, --web	Open in browser
--json	Output as JSON

Example:

sentry issue view FRONT-ABC

Issue: TypeError: Cannot read property 'foo' of undefined
Short ID: FRONT-ABC
Status: unresolved
First seen: 2024-01-15 10:30:00
Last seen: 2024-01-20 14:22:00
Events: 1,234
Users affected: 234

Latest event:
  Browser: Chrome 120
  OS: Windows 10
  URL: https://example.com/app

Open in browser:

sentry issue view FRONT-ABC -w

sentry issue explain

Analyze an issue’s root cause using Seer AI.

sentry issue explain <issue-id>

This command analyzes the issue and provides:

• Identified root causes
• Reproduction steps
• Relevant code locations

The analysis may take a few minutes for new issues.

Arguments:

Argument	Description
<issue-id>	The issue ID (numeric), short ID (e.g., PROJ-ABC), or short suffix

Options:

Option	Description
--org <org-slug>	Organization slug (required for short IDs if not auto-detected)
--project <project-slug>	Project slug (required for short suffixes if not auto-detected)
--force	Force new analysis even if one already exists
--json	Output as JSON

Examples:

# By numeric issue ID
sentry issue explain 123456789

# By short ID
sentry issue explain MYPROJECT-ABC --org my-org

# By short suffix (requires project context)
sentry issue explain G --org my-org --project my-project

# Force a fresh analysis
sentry issue explain 123456789 --force

Requirements:

• Seer AI enabled for your organization
• GitHub integration configured with repository access
• Code mappings set up to link stack frames to source files

sentry issue plan

Generate a solution plan for a Sentry issue using Seer AI.

sentry issue plan <issue-id>

This command requires that sentry issue explain has been run first to identify the root cause. It generates a solution plan with specific implementation steps to fix the issue.

Arguments:

Argument	Description
<issue-id>	The issue ID (numeric), short ID (e.g., PROJ-ABC), or short suffix

Options:

Option	Description
--org <org-slug>	Organization slug (required for short IDs if not auto-detected)
--project <project-slug>	Project slug (required for short suffixes if not auto-detected)
--cause <n>	Root cause ID to plan (required if multiple causes were identified)
--json	Output as JSON

Examples:

# After running explain, create a plan
sentry issue plan 123456789

# Specify which root cause to plan for (if multiple were found)
sentry issue plan 123456789 --cause 0

# By short ID
sentry issue plan MYPROJECT-ABC --org my-org --cause 1

Requirements:

• Root cause analysis must be completed first (sentry issue explain)
• GitHub integration configured for your organization
• Code mappings set up for your project