The Bitbucket integration pulls repositories, commits, and pull requests into Leanmote. It supports the same DORA and flow metrics as the other source-control integrations.
What Leanmote pulls from Bitbucket
Repositories you select.
Commits and authorship.
Pull requests with open/merge/close timestamps.
Note: Bitbucket integration is currently pull-based via the Bitbucket Cloud API. Webhooks are not configured automatically.
Connect Bitbucket
Open
Administration → Productivity Tools.Find Bitbucket under Source Control and click Connect.
Sign in to your Atlassian / Bitbucket account.
Authorize the requested scopes (listed below).
Select the repositories to track.
Click Save.
OAuth scopes requested
account— read your Bitbucket account profile so we can map identities to Leanmote teammates.team— read team membership for the workspaces you connect.repository— read repositories, commits, and pull-request metadata. The Bitbucketrepositoryscope gives broader access than the read-only data Leanmote actually uses; we never write back. If your security team needs the audit trail, every API call is logged on Bitbucket's side.
Sync cadence
Because Bitbucket sync is pull-based, expect minute-to-hour latency on new commits and PRs depending on your sync schedule. For higher-fidelity dashboards, prefer GitHub or GitLab where webhooks deliver events in seconds.
Common issues
Missing PR review data — confirm reviewers actually opened and approved the PR through Bitbucket; some review tools that overlay Bitbucket aren't captured.
Workspaces vs. repositories — Leanmote selects at the repository level. Adding a whole workspace's repos requires multi-select on connect.
Related articles
Integrations overview
Connect your first integrations
