Table of contents
Bitbucket Integration Overview
Bitbucket activity capture is rolling out. You can connect your Bitbucket workspace today, and WorkSights will register the connection and begin bringing commit, pull request, and code review activity onto the timeline as this capability completes rollout. If your workspace's timeline isn't showing Bitbucket activity yet, that's expected during rollout, not a sign anything is misconfigured.
Bitbucket is where a lot of engineering work happens outside Jira and GitHub. Connecting it brings commits, pull requests, and code review activity into the WorkSights timeline as Code-category work, the same category used for GitHub and Jira, so engineering activity reads consistently no matter which tool a team uses day to day.
For connection steps, see Bitbucket Setup.
What WorkSights Receives
Commits and pushes
Commit activity is attributed to the author recorded in Bitbucket, matched to a WorkSights user. Where a commit's author doesn't resolve directly, WorkSights also checks the commit's own author string as a fallback, since not every workstation's local git identity matches a Bitbucket account exactly.
Pull requests
Pull request creation, updates, merges, and declines appear as Code-category activity, attributed the same way as commits.
Code review
Approvals, change requests, and comments on a pull request — including when a comment is marked resolved — appear as activity tied back to the pull request.
Workspace members
WorkSights imports your Bitbucket workspace roster and matches members to WorkSights users by email, using Bitbucket's own member-lookup API.
WorkSights never reads file contents, diffs, or repository source code — only commit, pull request, and review metadata.
How Bitbucket Activity Appears
All Bitbucket activity uses the Code category, the same one GitHub and Jira use, so engineering signal reads consistently across every connected code platform.
Integration Page Overview
The Bitbucket integration page contains:
- Overview - Connection details and integration owner
- Users - Bitbucket workspace members mapped to WorkSights users
- Connections - Connected Bitbucket workspaces
Data Notes
WorkSights connects to Bitbucket using OAuth 2.0. The integration is read-only: WorkSights never writes to, modifies, or deletes anything in your Bitbucket workspace. Access does not include Pipelines, Runners, Snippets, or Wikis.
Troubleshooting
No activity is appearing after connecting
During rollout, this is expected — activity capture is still being completed for all workspaces. If your connection has been active for a while and you'd like a status update, contact us via in-app chat.
A workspace member isn't mapped
Confirm their Bitbucket email matches their WorkSights email in the Users tab.