Bitbucket Is the Forge That Came With Jira
The repo tab next to the ticket. Clone quality was never the sale.
[ essay ]
Bitbucket is the git host that arrived with Jira. Atlassian sold a suite. The forge was the repo tab next to the ticket.1 I have opened Bitbucket as a user because the job’s Jira project linked there. Dark Heart Labs does not. mystic-bytes is GitHub. I have never been a Bitbucket admin for this studio, and I will not move the writing repo to please a Jira workflow I do not run.
The product history is honest about the bundle. Mercurial first, then Git. Cloud and Data Center. Pipelines as the CI that already knew your Atlassian account. People did not choose Bitbucket because git clone was nicer. They chose it because the issue key already lived in Jira and the pull request wanted to close that key. The forge is an accessory. That is not an insult. It is how a company that bills seats on work items attaches a remote.
Use Bitbucket when Jira is already the database of work and the org will not add a second identity graph. Use GitHub when the graph of code is the center. I keep the studio on GitHub because the work is the repo, not the ticket next door.
— JV · Dark Heart Labs.
References
-
Atlassian Support, “What is Bitbucket?” https://support.atlassian.com/bitbucket-cloud/docs/what-is-bitbucket/. Git hosting in the Atlassian suite — the forge that sits beside Jira, not instead of it. ↩