v2

latestOpenAPI 3.0.02026-08-013312111.4 MB

Issue tracker

List changes on an issue

Returns the list of all changes that have been made to the specified issue. Changes are returned in chronological order with the oldest change first.

Each time an issue is edited in the UI or through the API, an immutable change record is created under the /issues/123/changes endpoint. It also has a comment associated with the change.

Note that this operation is changing significantly, due to privacy changes. See the announcement for details.

Changes support filtering and sorting that can be used to search for specific changes. For instance, to see when an issue transitioned to "resolved":

$ curl -s https://api.bitbucket.org/2.0/repositories/site/master/issues/1/changes \
   -G --data-urlencode='q=changes.state.new = "resolved"'

This resource is only available on repositories that have the issue tracker enabled.

N.B.

The changes.assignee and changes.assignee_account_id fields are not a user object. Instead, they contain the raw username and account_id of the user. This is to protect the integrity of the audit log even after a user account gets deleted.

The changes.assignee field is deprecated will disappear in the future. Use changes.assignee_account_id instead.

get/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes

Query parameters

qstring

Query string to narrow down the response. See filtering and sorting for details.

sortstring

Name of a response property to sort results. See filtering and sorting for details.

Response

Returns all the issue changes that were made on the specified issue.

sizeinteger

Total number of objects in the response. This is an optional element that is not provided in all responses, as it can be expensive to compute.

pageinteger

Page number of the current results. This is an optional element that is not provided in all responses.

pageleninteger

Current number of objects on the existing page. The default value is 10 with 100 being the maximum allowed value. Individual APIs may enforce different values.

nextstring uri

Link to the next page if it exists. The last page of a collection does not have this value. Use this link to navigate the result set and refrain from constructing your own URLs.

previousstring uri

Link to previous page if it exists. A collections first page does not have this value. This is an optional element that is not provided in all responses. Some result sets strictly support forward navigation and never provide previous links. Clients must anticipate that backwards navigation is not always available. Use this link to navigate the result set and refrain from constructing your own URLs.