Hilbana
ES/EN

Bitbucket

Link Bitbucket Cloud Pull Requests to issues: move the state and attach the PR automatically.

Open the PR and the task moves by itself. If the branch carries the task's identifier, opening the pull request on GitHub or Bitbucket attaches it to the task and moves it to in progress; merging it closes the task. Without touching the board. Watch in the feed →

The Bitbucket integration does for Bitbucket Cloud what the GitHub one does: it connects your repositories’ activity to Hilbana issues.

What it is

You connect it in Settings → Bitbucket (admins only). You authorize Hilbana in Bitbucket and choose what to listen to:

  • The whole workspace: a single webhook covering all its repositories, including the ones you create later. You need to be a workspace admin in Bitbucket.
  • Only some repositories: one webhook per repository. Being admin of each one is enough.

Hilbana creates the webhooks for you; there’s nothing to set up by hand in Bitbucket. You can connect more than one Bitbucket workspace to the same Hilbana workspace.

What it’s for

When you work on a Pull Request whose branch contains an issue’s identifier (for example drapps-142-... → issue DRAPPS-142), Hilbana:

  • Attaches the PR to the issue (number, link, branch and state).
  • Moves the issue’s state: opening the PR moves it to an in progress state; merging it, to a completed state. If you decline it, the PR shows as closed and the issue keeps its state.
  • Fires your automations’ PR triggers: PR opened, PR merged and PR closed without merge. Bitbucket doesn’t say when a draft becomes ready, so “PR ready for review” only works with GitHub.
  • Uses the changes in merged PRs for a milestone summary, just like with GitHub.

How to use it

  1. In Settings → Bitbucket, click Connect Bitbucket and authorize Hilbana.
  2. Back in Hilbana, choose the Bitbucket workspace and what to listen to, and click Activate.
  3. Name your branches including the issue’s identifier (the issue’s Copy branch name button gives it to you ready-made).
  4. Open and merge PRs as usual: the issue updates itself.

Turning it off

The “Use the Git integration (GitHub and Bitbucket)” switch in Settings → General covers both: turning it off hides the Git section on tasks, the GitHub and Bitbucket entries in Settings and the PR triggers in automations.

Details

  • Bitbucket Cloud only. Bitbucket Data Center / Server isn’t supported.
  • Each connection signs its webhooks with its own secret: an event can only write to the Hilbana workspace the connection belongs to.
  • The Bitbucket authorization is stored encrypted and never shown. Hilbana acts with the permissions of the account that connected: if that person loses access in Bitbucket, reconnect with another account.
  • Disconnecting deletes the webhooks in Bitbucket and the link in Hilbana. You can also revoke access from your Bitbucket personal settings (OAuth section).
  • The transition only happens if the issue’s team has a state of that category.

Related: GitHub · Issues · Workflow states.