Home / Servers / Sentry API / update_organization_issues
Bulk Mutate an Organization's Issues
An MCP tool from the Sentry API server, hosted on mcp.hjlabs.in.
Bulk Mutate an Organization's Issues Bulk mutate various attributes on a maxmimum of 1000 issues. - For non-status updates, the id query parameter is required. - For status updates, the id query parameter may be omitted to update… [PUT /api/0/organizations/{organization_id_or_slug}/issues/]
Name on the gateway: sentry_api__update_organization_issues · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
organization_id_or_slug required | string | The ID or slug of the organization the resource belongs to. |
environment | array | The name of environments to filter by. |
project | array | The IDs or slugs of projects to filter by. Project slugs are unique within… |
id | array | The list of issue IDs to mutate. It is optional for status updates, in which… |
statsPeriod | string | The period of time for the query, will override the start & end parameters, a… |
start | string | The start of the period of time for the query, expected in ISO-8601 format.… |
end | string | The end of the period of time for the query, expected in ISO-8601 format. For… |
query | string | An optional search query for filtering issues. A default query will apply if… |
viewId | string | The ID of the view to use. If no query is present, the view's query and… |
sort | date | freq | inbox | new | recommended | trends | user | The sort order of the view. Options include 'Last Seen' (date), 'First Seen'… |
limit | integer | The maximum number of issues to affect. The maximum is 100. |
inbox required | boolean | If true, marks the issue as reviewed by the requestor. |
status required | resolved | unresolved | ignored | resolvedInNextRelease | muted | Limit mutations to only issues with the given status. * resolved * unresolved… |
statusDetails required | object | Additional details about the resolution. Status detail updates that include… |
substatus required | string | The new substatus of the issue. * archived_until_escalating *… |
hasSeen required | boolean | If true, marks the issue as seen by the requestor. |
isBookmarked required | boolean | If true, bookmarks the issue for the requestor. |
isPublic required | boolean | If true, publishes the issue. |
isSubscribed required | boolean | If true, subscribes the requestor to the issue. |
merge required | boolean | If true, merges the issues together. |
discard required | boolean | If true, discards the issues instead of updating them. |
assignedTo required | string | The user or team that should be assigned to the issues. Values take the form… |
priority required | low | medium | high | The priority that should be set for the issues * low * medium * high |
ignoreDuration required | integer | Ignore the issue for this many minutes. |
ignoreCount required | integer | Ignore the issue until it is seen this many more times. |
ignoreWindow required | integer | Window in minutes over which ignoreCount is measured. Maximum is 7 days. |
ignoreUserCount required | integer | Ignore the issue until it affects this many more users. |
ignoreUserWindow required | integer | Window in minutes over which ignoreUserCount is measured. Maximum is 7 days. |
snoozeDuration required | integer | Snooze the issue for this many minutes. |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "sentry_api__update_organization_issues",
"arguments": {
"organization_id_or_slug": "…",
"inbox": true,
"status": "…",
"statusDetails": "…",
"substatus": "…",
"hasSeen": true,
"isBookmarked": true,
"isPublic": true,
"isSubscribed": true,
"merge": true,
"discard": true,
"assignedTo": "…",
"priority": "…",
"ignoreDuration": 0,
"ignoreCount": 0,
"ignoreWindow": 0,
"ignoreUserCount": 0,
"ignoreUserWindow": 0,
"snoozeDuration": 0
}
}Or connect the Sentry API server directly, which lists 272 tools including this one:
claude mcp add --transport http hj-sentry-api https://mcp.hjlabs.in/mcp/sentry-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the bulk mutate an organization's issues tool with organization_id_or_slug set to ….