Sydney, Australia
2002
  |  By Hamreet Kaur
Developers use Bitbucket Cloud every day to turn plans into working software. Code lives in repositories, feedback happens in pull requests, and Bitbucket Pipelines helps teams validate changes before they move forward. For an AI assistant to help with this work, it needs access to the same information. Without a direct connection, developers have to gather pull request details, pipeline results, logs, and links before the assistant can help.
  |  By Arthy Vijayaraghavan
Last quarter, our AI reviewer told a developer who was fixing a CSS bug to rethink how their component fetched data. The comment was well written and confidently worded. It was also about code they hadn’t touched. That’s what tends to happen when you hand an agent every team’s review guidelines at once.
  |  By Arthy Vijayaraghavan
The hard part of a feature flag is rarely adding it. It is remembering to remove it months later, when the rollout is over, the original context has faded, and there is always a more urgent piece of work waiting. Since April 2026, one Atlassian team has used Agentic Pipelines to clean up their monthly backlog of stale feature flags. The workflow prepares the change and opens a pull request, while engineers still review and merge the pull request.
  |  By Sanchi Gupta
Finding code across your repositories in Bitbucket just got a major upgrade. We’ve rolled out code search in open beta for Bitbucket Cloud: a faster, more integrated search experience built to help you find code across your workspace without interrupting your workflow. For many developers, search is one of the fastest ways to explore an unfamiliar codebase, investigate an incident, audit API usage, or scope a refactor.
  |  By Edmund Munday
AI agents can help investigate failed builds, fix flaky tests and automate other development tasks. But setting up those agents has required more Pipelines configuration than it should. Agent-powered steps often need different compute, permissions and runtime settings from ordinary build and test steps. Until now, teams have either repeated those settings across every agent-powered step or tried to make one set of global defaults work for everything.
  |  By Rajkumar Singh
When a team relies on automated tests in CI/CD, knowing that tests ran is only the beginning. Understanding whether the suite is healthy, which tests need attention, and how a specific test has behaved over time — that’s what drives action. Bitbucket Tests is evolving to make those answers easier to find and give you tools to improve your test health.
  |  By Arthy Vijayaraghavan
Routine vulnerability fixes are rarely difficult in isolation. The interruption that they cause is the problem: pick up the ticket, trace the dependency, update the package or image, regenerate files, run the checks, open the pull request, then return after deployment to close the loop. That repeated handoff was a good candidate for automation with agentic pipelines. The goal was simple: start the day with a tested pull request instead of another ticket to pick up.
  |  By Darshan Ail
You shouldn’t have to hunt through a cluttered dashboard to understand where your code is deployed. The Deployments page is where teams turn for a quick answer: what is in test, what is in staging, what reached production, and what needs attention right now. The older page made that harder than it needed to be. Our new Pipelines Deployments page makes it easier to scan, filter, and act on.
  |  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 Atlassian
Tired of spreadsheet trackers, lost Slack requests, and SaaS sprawl? Learn how to turn your existing Atlassian stack—Jira, Confluence, and Jira Service Management—into a unified HR hub for recruiting, zero-touch onboarding, and compliance. Most companies run on Atlassian, but HR workflows often remain scattered across spreadsheets, endless email threads, and disconnected SaaS tools. The answer isn't another point solution or a costly rip-and-replace—it's connecting the systems you already have.
  |  By Atlassian
Dave Killeen will tell you, on record, that his relationship with AI has crossed into unhealthy territory. He also says he has never felt more alive, that he is 50 and feels 30, and that he sometimes waits for his two small children to go to bed so he can start a coding session. In between, he gives Axel Sooriah the most practical answer on this show yet to the question every product team is facing: your exec says "we need AI," and you have no idea what they actually want.
  |  By Atlassian
Jira Planner is an AI planning agent in Jira that turns high-level product requirements into ready-to-build plans (requirements, technical specs, and Jira work items) grounded in your actual codebase, architecture, and Confluence context. In this video, you'll see how Jira Planner brings due diligence to the pre-build phase, so engineers and AI coding agents start from a plan that reflects the real code instead of a vague prompt. It's useful for product managers, engineering leads, and developers who want to cut the rework that comes from AI guessing at requirements.
  |  By Atlassian
Enterprise AI is only useful when it actually runs in production, inside the tools teams already depend on. Getting there is harder than it sounds. Forward Deployed Engineers at Atlassian work directly inside some of the world's largest organizations, building AI-powered agents, connectors, and workflows on Atlassian's platform. They work alongside customers to understand the real constraints, design solutions that hold up at scale, and see them through to deployment.
  |  By Atlassian
In the Startup Stories with Atlassian series, we interview founders about their entrepreneurial journey, learn about the problems they are trying to solve, and explore how their teams are using Atlassian tools to grow and deliver value to their customers. In this episode of Startup Stories with Atlassian, Adam sits down with Stan Suchkov, Founder and CEO of Evolve, to explore why pivoting isn't the failure most founders fear – and why the best founders do it deliberately, quickly, and without losing their team in the process.
  |  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.

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.