Missing Public APIs in Bitbucket Cloud
Most of the plugin runs on Bitbucket's public 2.0 REST API. A few features rely on data and operations that the public API does not expose yet, and Atlassian decides which public APIs to build based on customer demand on its issue tracker — so voting for the issues below is the most effective way to get these features covered by the public API.
The July 2026 interruption is over. Atlassian resolved it on August 5, 2026, and all affected features work normally again. No action is needed on your side.
How to Vote
- Open an issue link below and sign in with your Atlassian account.
- Click Vote for this issue in the People panel on the right side of the issue page.
- Add a comment describing how your team uses the feature. Votes show Atlassian how many people need the API, and comments explain what it blocks — together they carry far more weight than either alone.
The Issues
| Issue | Feature |
|---|---|
| BCLOUD-21086 | Likes for comments |
| BCLOUD-23331 | The "My Work" scope — pull requests you authored or review, in a single request |
| BCLOUD-23904 | Submitting a review — publishing all your pending comments in one step |
| BCLOUD-23906 | Pull request activity, including task events |
| BCLOUD-23907 | Revision data for comments — without it the plugin cannot tell current comments from outdated ones |
| BCLOUD-23909 | Pull request attachments |
| BCLOUD-23911 | The list of unreviewed changes |
| BCLOUD-23912 | Default pull request description template |
| BCLOUD-23913 | Checking for pull request updates without refetching everything |
How These Features Work Today
The features listed above are the exception: the public API has no equivalent for them, so the plugin reads them from the same endpoints that the Bitbucket web interface uses. It has done so for many years, and these features work reliably day to day. Because those endpoints are outside the documented public API and do not accept API tokens, the plugin keeps them isolated from everything else, so they never block the rest of your work. Public API coverage would put them on the same officially supported footing as the rest of the plugin.
The July 2026 Interruption
For a few days at the end of July 2026, requests to these endpoints stopped succeeding for some accounts, and features such as pull request discussions and merge checks were temporarily unavailable. Atlassian support and the Bitbucket team investigated and resolved it on August 5, 2026 — our thanks to both teams for the quick turnaround.
The plugin now also adapts on its own if one of these endpoints is ever unavailable, as described below.
If a Feature Is Temporarily Unavailable
Browsing pull requests, viewing diffs, commenting, approving, and merging run on the public API and keep working. For the remaining features, the plugin detects this automatically and adapts:
- Features that have a public API equivalent switch to it, sometimes with less detail — for example, the plugin can no longer tell outdated comments from current ones.
- Features that have no equivalent are hidden. An action that depends on one explains what is unavailable and which Atlassian issue tracks the missing API.
- Everything returns to normal on its own once the data is available again.