When to use Bitbucket

Teams on Bitbucket Cloud can connect here for repo linkage, PR activity, and contributor matching. It’s most common when Bitbucket is still the system of record, or when you’re mid-migration and need attribution on both sides.

Connect

Bitbucket uses a workspace slug and a read-only workspace access token, not OAuth.

1. Add Bitbucket to your tech stack (onboarding Integrations step or Settings → Integrations).
2. Click Connect next to Bitbucket.
3. Enter your Bitbucket workspace slug (for example acme-eng).
4. Paste a read-only workspace access token with at least:
   • Repositories: Read
   • Pull requests: Read

   Use a workspace access token, not an app password. You can also enter an env reference such as env:BITBUCKET_TOKEN if your workspace is set up that way.

5. Click Test Connection. When it succeeds, click Connect.
6. Confirm status shows Connected.

You need permission to create workspace access tokens for that Bitbucket workspace.

After connect, the platform ingests pull requests and reviews from every repository in the workspace. You do not pick individual repos in the dialog.

Migrating from Bitbucket to GitHub

When both the GitHub App and Bitbucket are connected, productivity can see merges from both hosts during the transition. To avoid double-counting the same work, a workspace admin (or platform admin) can set a prefer GitHub cutover on Data coverage:

1. Open Settings → Data coverage.
2. On the Productivity (GitHub) card, set Prefer GitHub since to a UTC date and time, then Save.
3. Use Clear when you no longer need the dual-VCS window.

From that instant onward, the platform prefers GitHub for attribution. Bitbucket-only merges after the cutover are not attributed. Set the cutover when GitHub becomes the system of record for new work.

Org chart columns

If you upload an HR org chart CSV, optional columns help match people to Bitbucket activity:

• bitbucket_nickname
• bitbucket_uuid (preferred when you have it)

Disconnect

Remove the connection under Settings → Integrations. Past data stays; new events stop.