Sydney, Australia
2002
  |  By Rajkumar Singh
Tracking tests on non-default branches was one of the most requested capabilities during the Bitbucket Tests (beta). We heard you, and today, we’re shipping it. Most teams don’t ship from main. Integration happens on develop, stabilisation on staging, releases cut from release. Until now, Bitbucket Tests only tracked the tests from default(main) branch, leaving the branches that actually matter invisible. Multiple branch tracking in Tests changes that.
  |  By Hamreet Kaur
We launched Bitbucket Packages to give teams one place to manage code, pipelines, and artifacts, and we’ve been expanding it ever since, first with Maven and npm, then PyPI and NuGet. Every one of those packages has shared one trait: it lives inside a single repository and inherits that repository’s permissions. Most of the time, that’s exactly what you want. But it also means sharing a package across repositories has meant granting people access to source code they never needed to see.
  |  By Gaurav Sharma
You shouldn’t have to grant full repository admin rights just to let an engineer or release manager trigger a deployment. To solve the all-or-nothing access problem, Bitbucket Pipelines introduces custom deployment permissions (Beta). You can now gate specific environments to authorized users and groups, ensuring safer releases and easier compliance. Left: Add users and groups to gate deployments for this environment.
  |  By Rajkumar Singh
In January we launched Tests in Bitbucket Pipelines – a single place to track, organize, and understand your test health over time. In April we added automatic flaky test detection so unreliable tests get flagged before they slow your team down. But spotting a problem is only half the battle. Day to day, your team still needs to act on a test – track it as work, clean it up, or route it to the right person.
  |  By Rajkumar Singh
Earlier this year, we launched Merge Queues in open beta to help teams automate, sequence, and validate pull request merges. During the beta period, we incorporated feedback from hundreds of teams to improve reliability and simplify configuration. Today, we are excited to announce that Merge Queues is generally available for Standard and Premium plans on Bitbucket Cloud.
  |  By Ash Moosa
Bring your Codex agent into Bitbucket Pipelines. A few weeks ago, we announced support for Claude agents in Bitbucket Pipelines. Today, we’re adding OpenAI Codex as a supported agent. If your team is already using Codex on the desktop, you can now move that same workflow into your pipeline — triggered by a merge, a schedule, a failing build, or a pull request comment.
  |  By Ash Moosa
In November 2025, we introduced new triggers and workflows to Bitbucket Pipelines to help teams manage and scale complex CI/CD workflows. We later extended that foundation with additional event-based triggers for pipeline, deployment, and pull request events. We’re now extending that model with a new package-artifact-created trigger.
  |  By Ash Moosa
When we introduced native Pipelines authentication for Bitbucket Packages, we made it easier to publish artifacts from CI/CD without relying on personal credentials. Now we’re extending that integration further: package artifacts published through the Pipelines integration can display a Source Pipeline, making it easy to trace an artifact back to the pipeline run that created it.
  |  By Hamreet Kaur
If your team bIf your team builds with Python or.NET, your packages have likely lived separately from your code, stored in a registry with distinct login, permissions, and billing. Starting today, they don’t have to. Bitbucket Packages now supports the Python Package Index (PyPI) and NuGet, integrating Python and.NET package management into the platform where your team writes code, reviews pull requests, and runs pipelines.
  |  By Ash Moosa
You shouldn’t have to leave your PR list to know where your code is deployed. Yet, developers constantly lose time context-switching just to see if a change hit staging or production. To solve this, we are launching the Beta version of Deployment Status Tracking for your PRs. This feature surfaces live deployment statuses directly within your PR list view as code moves through your pipeline.
  |  By Atlassian
Most CI/CD pipelines are fragile bash scripts that break when things change. What if your pipeline could think? Agentic Pipelines lets you add AI agents as steps in Bitbucket Pipelines. In this video, I show an agent that reads a design spec from Confluence, generates frontend code, runs tests, and opens a PR, all inside a pipeline. With Agentic Pipelines, Bitbucket goes from a CI/CD platform to a full workflow and automation engine you can use far beyond builds and deploys.
  |  By Atlassian
Customer interviews are one of the most powerful ways to build better products — but they’re also time-consuming. In this video, Avinoam “Avi” Zelenko, Principal Product Manager at Atlassian, shares how he transformed the way he runs customer interviews using AI automation and Rovo agents. What used to take hours of coordination, note-taking, and manual summaries now happens automatically. By stitching together the Teamwork Collection and Slack, Avi built a workflow that captures conversations, summarizes insights, and shares them across teams in real time.
  |  By Atlassian
Bitbucket Pipelines already supports triggering on repository pushes and pull request pushes. But if you wanted to react to other events like a deployment finishing, a build failing, or a PR getting merged, you had to wire that up yourself with webhooks or external glue code. New trigger types let you define those conditions directly in your YAML. You can fire custom pipelines on events like pipeline-completed, deployment-completed, pullrequest-created, pullrequest-fulfilled, and more.
  |  By Atlassian
AI transformation doesn’t succeed without people at the center. At Atlassian, HR is leading the way. Our People team believes that the best AI culture isn’t mandated from the top. It’s built by meeting employees where they are, partnering with leaders across the business, and making AI part of how work gets done from day one. See how Atlassian’s HR team is building a culture of experimentation where everyone builds, and what that looks like in practice.
  |  By Atlassian
Bitbucket Pipelines lets you invoke child pipelines from a parent step, but until now there was no way to pass information between them. Variable sharing changes that. You can define variables in a parent step and pass them directly to child pipelines as custom pipeline variables. With dynamic step conditions, those child pipelines can make decisions at runtime based on the values they receive, like skipping a deployment when a security scan detects critical vulnerabilities.
  |  By Atlassian
What used to take months now takes weeks, and it’s changing what it means to build great products. At Atlassian, product managers and designers are using Rovo and Jira Product Discovery to move faster at every stage of the development lifecycle. From running deep research across all their tools and documents, to capturing ideas, surfacing insights, and prioritizing what to build next. AI is transforming how product decisions get made.
  |  By Atlassian
Your team's best ideas shouldn't get lost between the doc, the ticket, and the meeting recording — but that's exactly what happens when AI lives outside your workflow. Teamwork Collection by Atlassian puts AI agents and your team on the same page — literally. Ideas flow to execution, agents pull context from your actual projects, and the line between "human work" and "AI work" starts to disappear.
  |  By Atlassian
As organizations work to bring humans, agents, and automation together, teamwork is getting even more complex. If your AI strategy feels like a collection of one-off experiments layered onto disconnected tools and siloed knowledge, join Atlassian leaders to see how Teamwork Collection brings together Jira, Confluence, Loom, and Rovo into a connected foundation for human-AI collaboration at scale.
  |  By Atlassian
AI is transforming how businesses operate and leaders are being held to higher expectations. Service must be unified, intelligent, and resilient across your entire organization, not patched together and slowed down by legacy constraints. Learn how Atlassian’s AI-powered Service Collection, including Jira Service Management, Customer Service Management, Assets, and Rovo, enables teams to meet this moment.
  |  By Atlassian
It’s time to reimagine teamwork for the AI era. Join Atlassian leaders to hear how human-AI teams collaborating in one system of work will propel your entire organization forward. About Atlassian: Behind every great human achievement, there is a team. From medicine and space travel to disaster response and pizza deliveries, we help teams all over the planet advance humanity through the power of software. Our mission is to help unleash the potential of every team.

Tools for teams, from startup to enterprise. Atlassian provides the tools to help every team unleash their full potential.

Atlassian is a leading provider of collaboration, development, and issue tracking software for teams. With over 100,000 global customers (including 85 of the Fortune 100), we’re advancing the power of collaboration with products including Jira, Jira Service Desk, Jira Ops, Confluence, Hipchat, Bitbucket, Trello, OpsGenie, and more. Driven by honest values, an amazing culture, and consistent revenue growth, we’re out to unleash the potential of every team.