Code in the same estate as the work that asked for it.
Bitbucket holds repositories inside the Atlassian estate, connected to Jira work items and to the change records that authorize a release. Our work is migration from other hosts, branch and access model design, and connecting code to change control.
Bitbucket puts repositories inside the Atlassian permission model, next to the work items and the change records. We migrate into it and design the access model that comes with it.
What it is
Bitbucket holds repositories inside the Atlassian estate, connected to Jira work items and to the change records that authorize a release.
It is for organizations consolidating tooling, or ones that want the link between a work item, a change record, and the commit that implemented it to exist without an integration in the middle.
What it does
Repositories in the permission model
Access is governed with the rest of the estate rather than in a separate product with a separate list.
Work items linked to changes
The trace from a request to the commit exists without a synchronization job maintaining it.
Where it fits
L2, platform and migration. It is part of the system of work, and the access model on a repository is an identity decision that most organizations make per repository over years. That is the debt an agent rollout later collides with.
What we do with it
Migration from another host
Repository and history migration, with the access model designed rather than copied.
Branch and permission design
A consistent protection model, which is the prerequisite for anything automated touching a repository.
Connecting code to change control
Where a release needs an approval record, the two systems have to agree on what approved means.
Where it earns its place
An organization consolidating source hosts
Two or three hosts after acquisitions, where the real cost is three access models rather than three tools.
A team preparing for dev agents
Consistent branch protections are what make an agent rollout a configuration rather than a risk assessment.
Proof
World Class Software Development Finalist, 2024-2025
Atlassian Partner Awards, 2024-2025
Questions we get
Do you migrate history?
Is this worth doing on its own?
Licensing
Repository hosting is licensed per user and frequently overlaps with an incumbent still being paid for during a transition. That reconciliation sits with the rest of the estate in licensing and renewals.