Issues & support
Set up Bitbucket
Connect Bitbucket Cloud to make issues and pull requests searchable — each becomes a document with its description and comment thread, tied to its repository and author, so “was that bug already reported” and “why was that change declined” answer from the workspace itself. Read-only.
Before you start
- id.atlassian.com → Security → API tokens → Create API token with scopes, granting READ on repositories, issues and pull requests — those three are all it uses. Copy it right away; it's shown once.
- Legacy Bitbucket app passwords still work but retire in July 2026 — use an API token for new setups. Only reads are ever issued; nothing is written to Bitbucket.
- Documents → Bitbucket, enter Workspace — the first part after bitbucket.org/ in any repository's address.
- Username or Atlassian email: with an API token, your Atlassian account email; with a legacy app password, your Bitbucket username (Personal settings → Account settings shows it).
- Paste the credential as API token / app password.
- Repositories: optional repo slugs (the short name after the workspace in a repository's URL), one per line — blank syncs every repository in the workspace.
- Choose access groups, Test, then Sync.
What comes in
- Each issue becomes a document titled workspace/repo #number: title — state, reporter, assignee where set, last-updated date, the description and the comment thread, each comment with who wrote it and when.
- Each pull request becomes a document the same way — state (open, merged, declined or superseded), author, last-updated date, description and comments; merged and declined history comes in, not just open work.
- Each repository also becomes a concept card carrying its description and how many issues and pull requests it contributed.
- Code, commits and diffs are not read.
Access
Access is allow-only: the groups chosen on the source cover everything Bitbucket brings in — Bitbucket's own repository permissions are not mirrored.
Caps per sync: 500 repositories, and per repository 3,000 issues and 3,000 pull requests, with up to 500 comments per item — Sync notes any cap it hits, and the rest are not synced. Comment threads are read for the first 300 pull requests a sync reaches; later ones sync without their thread, and Sync says so. A repository with its issue tracker turned off simply syncs no issues — that's not an error — and a listed slug that doesn't exist is noted and skipped. Test says how many repositories it reached; it fails with a specific reason — rejected credentials, a workspace it can't find, or none of the listed repositories being reachable. A sync Bitbucket keeps rate-limiting stops with “the next sync catches up”. Revoke access any time by deleting the token under Security → API tokens at id.atlassian.com.
Last updated 20 Sep 2026