GET /repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes
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.
Servers
- https://api.bitbucket.org/2.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
issue_id |
String | Yes |
The issue id |
repo_slug |
String | Yes |
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: |
workspace |
String | Yes |
This can either be the workspace ID (slug) or the workspace UUID
surrounded by curly-braces, for example: |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
q |
String | No |
Query string to narrow down the response. See filtering and sorting for details. |
sort |
String | No |
Name of a response property to sort results. See filtering and sorting for details. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.