Bulk Mutate an Organization's Issues

PUT /api/0/organizations/{organization_id_or_slug}/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 issues that match the filtering. If any IDs are out of scope, the data won't be mutated but the endpoint will still produce a successful response. For example, if no issues were found matching the criteria, a HTTP 204 is returned.

Path Parameters

organization_id_or_slug (string) REQUIRED: The ID or slug of the organization the resource belongs to.

Query Parameters:

environment (array(string))

The name of environments to filter by.

project (array(integer))

The IDs of projects to filter by. -1 means all available projects. For example, the following are valid parameters:

/?project=1234&project=56789
/?project=-1

id (array(integer))

The list of issue IDs to mutate. It is optional for status updates, in which an implicit update all is assumed.

query (string)

An optional search query for filtering issues. A default query will apply if no view/query is set. For all results use this parameter with an empty string.

viewId (string)

The ID of the view to use. If no query is present, the view's query and filters will be applied.

sort (string)

choices:

date
freq
inbox
new
trends
user

The sort order of the view. Options include 'Last Seen' (date), 'First Seen' (new), 'Trends' (trends), 'Events' (freq), 'Users' (user), and 'Date Added' (inbox).

limit (integer)

The maximum number of issues to affect. The maximum is 100.

Body Parameters

inbox (boolean) REQUIRED

If true, marks the issue as reviewed by the requestor.

status (string) REQUIRED

Limit mutations to only issues with the given status.

resolved
unresolved
ignored
resolvedInNextRelease
muted

statusDetails REQUIRED

Additional details about the resolution. Status detail updates that include release data are only allowed for issues within a single project.

substatus (string) REQUIRED

The new substatus of the issue.

archived_until_escalating
archived_until_condition_met
archived_forever
escalating
ongoing
regressed
new

hasSeen (boolean) REQUIRED

If true, marks the issue as seen by the requestor.

isBookmarked (boolean) REQUIRED

If true, bookmarks the issue for the requestor.

isPublic (boolean) REQUIRED

If true, publishes the issue.

isSubscribed (boolean) REQUIRED

If true, subscribes the requestor to the issue.

merge (boolean) REQUIRED

If true, merges the issues together.

discard (boolean) REQUIRED

If true, discards the issues instead of updating them.

assignedTo (string) REQUIRED

The user or team that should be assigned to the issues. Values take the form of <user_id>, user:<user_id>, <username>, <user_primary_email>, or team:<team_id>.

priority (string) REQUIRED

The priority that should be set for the issues

low
medium
high

Scopes

You need to authenticate via bearer auth token.

<auth_token> requires one of the following scopes:

event:admin
event:write

Copied

curl https://sentry.io/api/0/organizations/{organization_id_or_slug}/issues/ \
 -H 'Authorization: Bearer <auth_token>' \
 -X PUT \
 -H 'Content-Type: application/json' \
 -d '{}'

RESPONSESCHEMA

Copied
{
  "assignedTo": {
    "type": "user",
    "id": "1",
    "name": "John Doe",
    "email": "john.doe@example.com"
  },
  "discard": false,
  "hasSeen": true,
  "inbox": true,
  "isBookmarked": false,
  "isPublic": true,
  "isSubscribed": true,
  "merge": {
    "children": [
      "11",
      "12",
      "13"
    ],
    "parent": "10"
  },
  "priority": "medium",
  "shareId": "123def456abc",
  "status": "ignored",
  "statusDetails": {
    "ignoreDuration": 100,
    "ignoreCount": 10,
    "ignoreWindow": 60,
    "ignoreUserCount": 10,
    "ignoreUserWindow": 60,
    "inNextRelease": false,
    "inUpcomingRelease": false,
    "inRelease": "1.0.0",
    "inCommit": {
      "commit": "123def456abc",
      "repository": "getsentry/sentry"
    }
  },
  "subscriptionDetails": {
    "disabled": false,
    "reason": "mentioned"
  },
  "substatus": "archived_until_condition_met"
}

Was this helpful?