Bitbucket Cloud
Konductro integrates with Bitbucket Cloud as a per-project git provider — branches, pull requests, ticket-spec push, and PR status sync all work the same way they do for Azure DevOps and the Konductro-managed Gitea backend. Bitbucket Server / Data Center is not supported; this integration is Cloud only.
What Syncs
| Data | Direction | Detail |
|---|---|---|
| Branches | Konductro to Bitbucket | Feature branches created via the Bitbucket REST API when a developer starts work |
| Ticket specs | Konductro to Bitbucket | .tickets/TICKET-KEY.md files pushed to the branch via the Bitbucket multipart commit API |
| Pull requests | Konductro to Bitbucket | PRs created with title, description, and acceptance criteria checklist |
| Reviewers | Konductro to Bitbucket | Auto-assigned reviewer added to the PR via the reviewer's stored Atlassian Account UUID |
| PR status | Bitbucket to Konductro | Open / merged / declined / superseded states polled on view load |
Authentication
Bitbucket Cloud authentication is per-user. Each developer who works on a Bitbucket-backed project adds their own Atlassian API token to their Konductro profile. Konductro authenticates to Bitbucket as that user using HTTP Basic auth with email:apiToken — no shared service account, no workspace-level token, no OAuth flow.
Setup
Step 1: Create an Atlassian API token
Sign in to id.atlassian.com → Security → API tokens using the Atlassian account that has access to the Bitbucket workspace.
Click "Create API token with scopes", give it a descriptive label (e.g. "Konductro"), and on the scopes screen select exactly the following:
| Scope | Why it's needed |
|---|---|
read:account | Fetches your Atlassian Account UUID — used when you're assigned as a PR reviewer |
read:workspace:bitbucket | Read workspace metadata |
read:repository:bitbucket | List repos and branches |
write:repository:bitbucket | Create branches and push the ticket spec file |
read:pullrequest:bitbucket | Read PR state for status sync |
write:pullrequest:bitbucket | Create PRs and assign reviewers |
read:account sits under Atlassian Account, the rest under Bitbucket. The Bitbucket-specific read:user:bitbucket is an acceptable substitute for read:account.
Copy the token — it is shown only once.
Step 2: Add the credential in Konductro
In your Konductro profile, under Git Credentials, click Add Credential and select Bitbucket Cloud. Fill in:
- Workspace — your Bitbucket workspace slug. This is the segment between
bitbucket.org/and the next/in any repo URL (e.g.acme-team), not the display name. - Atlassian Email — the email on your Atlassian account (the
emailhalf of the Basic auth pair). - API Token — the token you copied in Step 1.
Konductro validates the credentials against the workspace before saving and fetches your Atlassian Account UUID at the same time.
Step 3: Set the project's git provider
When creating a project, pick Bitbucket Cloud as the git provider. No project-level workspace field is required — workspaces are captured per-repo at link time. For existing projects, change the provider in Project → Git → Settings.
Step 4: Link your repos
In Project → Git, click Link Existing Repository, choose Bitbucket Cloud, pick the credential to use, and select the repos to link from the workspace's repo list. Konductro stores a typed identifier { provider: 'bitbucket', workspace, repo } on each linked repo so cross-provider operations route correctly.
Per-User Token Model
Every developer who needs git operations on a Bitbucket-backed project must configure their own Bitbucket API token in their Konductro profile. Konductro resolves the calling user's stored credential before each git operation — there is no shared service account.
Practical consequences:
- Branch creation, file push, and PR creation are attributed to the developer who initiated the action.
- Reviewer assignment uses the reviewer's Atlassian Account UUID — for auto-reviewer to land on the PR, both the PR creator and the reviewer must have Bitbucket credentials configured.
- Token rotation is per-user: revoke at id.atlassian.com and re-add in your profile.
Not Supported
- Bitbucket Server / Data Center. Cloud only.
- OAuth. Per-user API tokens only.
- Workspace / Repository Access Tokens (the Bearer-style tokens generated from Bitbucket workspace settings). Konductro authenticates with Basic auth using the personal API token model.
- Bitbucket Pipelines integration. PR status syncs, but CI runs are not surfaced in Konductro.
- Bitbucket Issues sync. Konductro tickets are the source of truth.