Bitbucket

Connect Bitbucket Cloud and every pull request or commit that mentions an issue key (like HRB-142) shows up on that issue, kept up to date as it's reviewed, built and merged. Open Integrations → Bitbucket → Configure to set it up. You need permission to manage integrations.

Connecting Bitbucket

There are two ways to connect:

• Connect Bitbucket signs in with your Bitbucket account (where available). Deckbell then sees the repositories you're an admin of.
• Access token works everywhere. Enter your workspace (the part after bitbucket.org/ in your repositories' addresses) and one of:
  • a workspace, project or repository access token (Bitbucket settings → Access tokens) with the Repositories: Admin, Pull requests: Read and Webhooks: Read and write scopes, or
  • an Atlassian API token for Bitbucket with the same scopes, together with your Atlassian account's email under Atlassian account email.

Linking repositories

Under Repositories, search for a repository and choose Link. Deckbell adds a webhook to it for pull requests, pushes and build statuses. Every delivery is signed with a secret only Deckbell and Bitbucket know, so nobody else can send it updates.

If Bitbucket doesn't let Deckbell add the webhook (for example, the account isn't an admin of the repository), Deckbell shows the webhook URL and secret once. A repository admin can add it in Repository settings → Webhooks with these triggers turned on: Push; Pull request created, updated, merged and declined; Build status created and updated.

Unlink removes the repository and its webhook. Disconnect removes Bitbucket from the workspace, along with the webhooks Deckbell added.

Pull requests on issues

A pull request is linked to an issue when its source branch, title or description mentions the issue's key, for example a branch named hrb-142-proration or "Fixes HRB-142" in the description. Linked pull requests appear with GitHub pull requests and GitLab merge requests in the issue's right sidebar, with their number and state: open, draft, merged or closed (declined). Click one to open it in Bitbucket. See Issue details.

Pipelines status

Bitbucket Pipelines, and any other CI that reports build statuses to Bitbucket, show as a badge under the pull request: Checks passing, N failing or Checks running. Click it to open the build. The badge follows the pull request's latest commit.

Commits

Commits pushed to a linked repository whose message mentions an issue key (for example "Round prorated amounts, refs HRB-142") are listed under Commits on that issue, with a link to the commit in Bitbucket.