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 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
The ID or slug of the organization the resource belongs to.
Query parameters
The name of environments to filter by.
The IDs or slugs of projects to filter by. Project slugs are unique within each organization. Omit this parameter to include all accessible projects. -1 is also accepted to include all accessible projects. For example, the following are valid parameters:
- /?project=1234&project=56789
- /?project=android&project=javascript-react
- /?project=-1
The list of issue IDs to mutate. It is optional for status updates, in which an implicit update all is assumed.
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.
The ID of the view to use. If no query is present, the view's query and filters will be applied.
The sort order of the view. Options include 'Last Seen' (date), 'First Seen' (new), 'Trends' (trends), 'Events' (freq), 'Users' (user), 'Date Added' (inbox), and 'Recommended' (recommended).
The maximum number of issues to affect. The maximum is 100.