Overview

The Bitbucket integration lets Sizemotion capture commits, pull requests, and pipeline statuses so you can talk about delivery confidence during reviews and check-ins. The Integrations Hub (/integration/manage) highlights connector health, quick actions, and the Bitbucket card contains the status badge you need to verify the sync.

Why it matters

  • Tracks repo activity, builds, and pull requests without leaving Sizemotion.
  • Links delivery work to reviews, goals, and OKRs for context-rich conversations.
  • Helps managers spot blocked builds or long-running pull requests early.

Sync surface

  • Repository mirror: Pulls commit metadata and branch history from the repositories the configured credentials can see.
  • Pull request detail: Imports open, merged, and declined pull requests plus reviewers and merge status.
  • Pipeline visibility: Shows the latest pipeline run per repository so you know when a build last succeeded.
  • Webhook refresh: Optional webhooks keep the sync near real-time when batch polling is not enough.

Setup

  1. Visit the Integrations Hub: Go to /integration/manage and click the Bitbucket connector card to see health status and quick links.
  2. Gather credentials: Create an App Password in Bitbucket with repository, pullrequest, and webhook scopes, plus account read access if you need workspace data.
  3. Enter details in Sizemotion: Open /integration/bitbucket (or the config flow from the hub), paste the username + app password, and select the repositories or project filters you want to sync.
  4. Enable webhooks (optional): Copy the webhook endpoint from the config page and register it on the Bitbucket workspace. Store the webhook secret in Sizemotion for payload validation.

Security & permissions

  • Only admins can configure or update the Bitbucket connector via /integration/bitbucket or the hub.
  • App passwords are encrypted in transit and at rest; rotate them if teams change or credentials leak.
  • Webhook secrets are signed on delivery and validated by the controller to prevent tampering.
  • Audit logs capture who connected, reconnected, or disabled the integration.

Workflow & visibility

  • Overview page: The /integration/bitbucket route lists synced repos with last activity timestamps, open pull requests, and build statuses.
  • Reports: Pipeline results and merge evaluations feed into performance reviews and delivery retrospectives.
  • Alerts: Sizemotion surfaces failed syncs, expired credentials, and webhook rejections so you can resolve them before data gaps appear.

Monitoring

  • Status badges on the Integrations Hub show whether Bitbucket is healthy (green), needs attention (amber), or is disabled (gray).
  • Error details explain whether Bitbucket returned 401 (bad credentials), 403 (missing scopes), or webhook validation failures.
  • Manual sync options exist on the configuration page for forced refreshes if you need immediate data.

Troubleshooting

  • "Authentication failed": Verify the App Password covers repository and pullrequest scopes and the username matches the owner.
  • Webhook rejects payloads: Re-enter the webhook secret on the config page and confirm Bitbucket is sending the same secret.
  • Disabled connector: Re-enable from /integration/manage/bitbucket or recreate the configuration.
  • No repositories appear: Ensure the app password user has access to the repositories or workspace filters configured in Sizemotion.

FAQs

Can I filter which repositories sync?

Yes, choose projects or repositories in the config page. Sync honors the filters before fetching data.

Do you support Bitbucket Server?

Not yet—currently only Bitbucket Cloud is supported. Contact support if you need a Server/Data Center connector.

What if the app password expires?

Generate a new app password in Bitbucket, then paste it on the config screen. Sizemotion will verify the credentials before saving.

Next steps