> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/integration/connecting-tools/bitbucket.md).

# Bitbucket

The Bitbucket connector imports pull requests, commits and code review activity from Bitbucket Cloud so your delivery and review metrics reflect real repository activity.

## Authentication

Logilica connects to Bitbucket using **OAuth**. Authorise Logilica through Bitbucket and Logilica reads your repository data using the granted access token. Logilica only reads the relevant data and never stores your password. Logilica requests read-only access to your Bitbucket Cloud workspaces.

See [Connecting Tools](/integration/connecting-tools.md) for the general installation flow.

## What's Imported

For each connected repository, Logilica imports:

* **Pull requests** — title, description, author, source branch, created/updated/closed timestamps, and who closed (merged) the pull request
* **Commits** on each pull request, including author, commit message and commit time
* **Comments and inline comments** — including the file an inline comment applies to
* **Approvals** — who approved and when
* **Changed-file counts** — the number of files changed in the pull request
* **Contributor identities** — display name and account for every author, reviewer and merger, used for identity resolution and team assignment

## How Logilica Maps the Data

### Pull request state

Logilica tracks each pull request through its lifecycle — open, reviewed, approved, merged or declined — combining Bitbucket's status with review activity.

### Review lifecycle

Logilica captures who reviewed each pull request, which files they reviewed, approvals, and review timing from Bitbucket's comments and approval events.

### Linking pull requests to tickets

Logilica recognises issue keys in commit messages, pull request titles and branch names to connect code changes to planning work. See [Linking Pull Requests and Tickets](/integration/linking-pull-requests-and-tickets.md) for how this works and how to format references.

## Good to Know

* **Kept in sync automatically.** After the initial import, Logilica refreshes this connection on a regular schedule — you don't need to re-trigger imports.
* **First import covers the last 6 months.** Only pull requests updated in the last 6 months are imported on the first scan. Importing older history requires a configuration change by Logilica — contact support.
* **Bitbucket does not expose user email addresses**, so contributor identities are matched on display name and account rather than email. This can affect identity resolution where the same person uses different accounts.
* **Bitbucket has no draft pull requests**, so no pull request is imported as a draft.
* **Releases are not imported from this connector.** Release detection for DORA on Bitbucket relies on other sources such as build data or pull request patterns. See [Release Detection](/configuration/release-detection.md) and [DORA Configuration](/configuration/dora-configuration.md).
* **Comments are counted, not stored verbatim.** Logilica records comment counts, reviewers and which files were reviewed for metrics.