List all organizations that the user has access to in Sentry. Use this tool when you need to: - View all organizations in Sentry

List all teams in an organization in Sentry. Use this tool when you need to: - View all teams in a Sentry organization

Retrieve a list of projects in Sentry. Use this tool when you need to: - View all projects in a Sentry organization

List all issues in Sentry. Use this tool when you need to: - View all issues in a Sentry organization If you're looking for more granular data beyond a summary of identified problems, you should use the `search_errors()` or `search_transactions()` tools instead. <examples> ### Find the newest unresolved issues in the 'my-project' project ``` list_issues(organizationSlug='my-organization', projectSlug='my-project', query='is:unresolved', sortBy='last_seen') ``` ### Find the most frequently occurring crashes in the 'my-project' project ``` list_issues(organizationSlug='my-organization', projectSlug='my-project', query='is:unresolved error.handled:false', sortBy='count') ``` ### Find the oldest unresolved issues in the 'my-project' project ``` list_issues(organizationSlug='my-organization', projectSlug='my-project', query='is:unresolved', sortBy='first_seen') ``` </examples> <query_syntax> Use the tool `help('query_syntax')` to get more information about the query syntax. There are some common query parameters that are useful for searching errors: - `is:unresolved` - Find unresolved issues - `release:[1.0, 2.0]` - Find issues in a specific release - `release:latest` - Find issues in the latest release only </query_syntax> <hints> If only one parameter is provided, and it could be either `organizationSlug` or `projectSlug`, its probably `organizationSlug`, but if you're really uncertain you should call `list_organizations()` first. </hints>