Demo
Đăng nhập

Bulk Mutate a List of Issues

Bulk mutate various attributes on issues. The list of issues to modify is given through the id query parameter. It is repeated for each issue that should be modified.

  • For non-status updates, the id query parameter is required.
  • For status updates, the id query parameter may be omitted for a batch "update all" query.
  • An optional status query parameter may be used to restrict mutations to only events with the given status.

The following attributes can be modified and are supplied as JSON object in the body:

If any ids are out of scope this operation will succeed without any data mutation.

Path Parameters

organization_slug (string)
REQUIRED

The slug of the organization the issues belong to.

project_slug (string)
REQUIRED

The slug of the project the issues belong to.

Query Parameters:

id (integer)

A list of IDs of the issues to be mutated. This parameter shall be repeated for each issue. It is optional only if a status is mutated in which case an implicit update all is assumed.

status (string)

Optionally limits the query to issues of the specified status. Valid values are "resolved", "unresolved" and "ignored".

Body Parameters

status (string)

The new status for the issues. Valid values are "resolved", "resolvedInNextRelease", "unresolved", and "ignored".

statusDetails (object)

Additional details about the resolution. Valid values are "inRelease", "inNextRelease", "inCommit", "ignoreDuration", "ignoreCount", "ignoreWindow", "ignoreUserCount", and "ignoreUserWindow".

ignoreDuration (integer)

The number of minutes to ignore this issue.

isPublic (boolean)

Sets the issue to public or private.

merge (boolean)

Allows to merge or unmerge different issues.

assignedTo (string)

The actor id (or username) of the user or team that should be assigned to this issue.

hasSeen (boolean)

In case this API call is invoked with a user context this allows changing of the flag that indicates if the user has seen the event.

isBookmarked (boolean)

In case this API call is invoked with a user context this allows changing of the bookmark flag.

Scopes

<auth_token> requires the following scopes:
  • project:write
PUT /api/0/projects/{organization_slug}/{project_slug}/issues/
curl https://sentry.io/api/0/projects/{organization_slug}/{project_slug}/issues/ \
 -H 'Authorization: Bearer <auth_token>' \
 -X PUT \
 -H 'Content-Type: application/json' \
 -d '{"isPublic":false,"status":"unresolved"}'
RESPONSESCHEMA
{
  "isPublic": false,
  "status": "unresolved",
  "statusDetails": {}
}