Bitbucket
Connect Bitbucket Cloud to bring code activity into recaps, planning, Pull Requests, and Insights.
Bitbucket is in private beta and enabled per workspace. The integration supports Bitbucket Cloud OAuth through bitbucket.org. Bitbucket Data Center and self-hosted instances are not supported.
Connect Bitbucket
Each developer connects their own Bitbucket Cloud account. This keeps commits, pull requests, comments, and repository activity tied to the right person.
To connect, open Bitbucket integration settings and sign in on bitbucket.org. After authorization, you return to the dashboard with the connection linked to the current workspace.
If the Bitbucket card still shows Coming Soon, your workspace does not have the beta enabled yet.
What Bitbucket adds
| Bitbucket activity | What it does |
|---|---|
| Commits | Help derive completed work and delivery context. |
| Pull requests | Appear in Merge & Pull Requests with other review work. |
| Push events | Keep commit activity current through Bitbucket webhooks. |
| Pull request events | Track review and merge state for delivery and measurement. |
| Comments | Add review context where Bitbucket permissions allow it. |
Open pull requests can appear in planned work. Merged pull requests can move into completed work. For capture behavior, see Captured Work.
Commit summaries
Commits from connected repositories can be grouped into daily work summaries. If commit comments are enabled, the summary can also be posted back as a Bitbucket commit comment.
Settings
Change these in Bitbucket settings.
| Setting | What it controls |
|---|---|
| Include personal repositories | Includes repositories from your personal Bitbucket workspace. Off by default. |
| Disable commit comments | Prevents summaries from being posted back as Bitbucket commit comments. |
| Exclude workspaces | Stops activity from selected Bitbucket workspaces from feeding recaps, planning, and insights. |
| Exclude repositories | Stops selected Bitbucket repositories from being tracked. |
Bitbucket does not use the GitHub contribution scanning setting. Personal repositories come from your user workspace. Team repositories follow Bitbucket workspace and repository access.
Reconnects preserve excluded workspaces, excluded repositories, personal repository settings, and commit comment preferences.
Where activity appears
Bitbucket activity appears in Recaps, Merge & Pull Requests, Insights, and Pull Request Flow. Link it to Initiatives when code should roll up to planned work, and track defects or incidents as Bugs.
Security and access
We never ask for your Bitbucket password. The integration uses Bitbucket Cloud OAuth and requests Bitbucket API access during connection.
Bitbucket OAuth tokens expire and refresh automatically when possible. If refresh fails or the grant is revoked, reconnect Bitbucket.
Bitbucket controls which workspaces and repositories your account can access. We use Bitbucket metadata to build summaries and work context. We do not store your repository source code.
To disconnect completely, revoke the OAuth grant from your Bitbucket user settings or remove the integration from the workspace.