# /2.0/repositories/{}/{}/issues stops working

Calls to /2.0/repositories/{id}/{id}/issues* on Bitbucket Cloud API stopped working on August 20, 2026.

On August 20, 2026, Bitbucket Cloud API removed the endpoints supporting its Issue Tracker. Requests to /2.0/repositories/{id}/{id}/issues* now fail because these endpoints are fully removed. Calls targeting this path no longer receive responses from the service.

## What to use instead

Move issue tracking to Jira or another tracker and call its API instead. Because Bitbucket no longer provides an issue tracker, selecting and moving to Jira or an alternative tracker requires a product decision.

Bitbucket has no issue tracker anymore: moving the issues to Jira or another tracker is a product decision.

- API: Bitbucket Cloud API (api.bitbucket.org)
- Kind: Endpoint removal
- Takes effect: August 20, 2026
- Calls after that day: fail
- Calls it hits: `/2.0/repositories/{id}/{id}/issues*`
- Source: [Announcement](https://developer.atlassian.com/cloud/bitbucket/changelog/)
- Verified: November 6, 2026, against Bitbucket Cloud API's own pages
- Page: https://www.okapi.bot/providers/bitbucket-cloud-api/breaking-changes/2-0-repositories-issues-stops-working/

## Bitbucket Cloud API's words

> the API endpoints that support Issue Tracker are now fully removed.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent