Sydney, Australia
2002
  |  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 Hamreet Kaur
We’re excited to announce that immutable tags are now available for the Bitbucket Packages container registry. With immutable tags, workspace admins can set container image tags from being overwritten, moved, or modified after they’re first pushed.
  |  By Marcos Sampaio
In December, we shared our plans to introduce pricing for self-hosted runners. You told us loud and clear that a free option matters. Today, as Premium Runners become generally available, we are happy to share that we will continue to have a free tier, which includes the use of up to 100 self-hosted runners as part of your plan. If your team needs more scale, dedicated support, or advanced management features, you can upgrade to Premium Runners when you’re ready.
  |  By Edmund Munday
Last month, we introduced Agentic Pipelines, a new way to orchestrate AI agents to automatically, and routinely, handle the repetitive engineering chores so you can get back to solving the fun, cool problems. When we launched, Agentic Pipelines supported Atlassian’s developer AI agent, Rovo Dev. Today, we’re opening up Agentic Pipelines to even more teams: You can now run agentic steps in your pipeline with Claude as the provider.
  |  By Rajkumar Singh
At Atlassian, we use Merge Queues to ship frequent changes with confidence and streamline pull request merges. Across some of our busiest codebases, Merge Queues have sharply reduced incident frequency and turned merging from a stressful bottleneck into a background task. Today, most of our largest repositories rely on Merge Queues—over 70 large repos across products like Jira, Rovo, Trello, and others—having safely landed 30,000 pull requests since adopting Merge Queues Beta last quarter.
  |  By Edmund Munday
Your CI/CD pipeline doesn’t have to live in a YAML file anymore. With on-demand pipelines, you can generate pipeline definitions programmatically, from scripts, services, or automation tools – and execute them instantly via the Pipelines API. No commit. No pull request. No static configuration to modify. Just build the YAML your situation demands and run it.
  |  By Edmund Munday
As part of an initiative to increase the flexibility and power of child pipelines, we are happy to announce that Bitbucket Pipelines will now allow you to share artifacts between parent and child pipelines. This feature extends the use-cases for child pipelines, allowing a greater degree of coordination between parent and child and the use of child-pipelines as modular pieces of processing for larger operations with artifacts. Here’s how it works.
  |  By Rajkumar Singh
Teams are shipping more code, faster than ever, as they increasingly automate their processes with CI/CD and AI. But high-velocity pull-request workflows and large monorepos, where many PRs are merged continuously, are feeling the pain as they grow: pull requests race to merge before the branch changes again, “green” builds still break due to semantic merge conflicts, and developers are stuck babysitting merges instead of building features.
  |  By Edmund Munday
Bitbucket Pipelines has always been an engine for automating more than just CI/CD, but today, Pipelines takes a first step towards a full agentic automation platform for all the manual, tedious, repetitive work that happens before and after code creation. You’ve probably seen the stat: Development teams spend 84% of their day doing things other than building features. A lot of this work is: This work matters, but it’s not very fun.
  |  By Sanchi Gupta
Why did your build fail? Ask Rovo, get a clear answer, and even a way to fix it, from anywhere in Bitbucket Pipeline debugging is one of the most common and most painful parts of the development workflow. In our Atlassian research: AI adoption is rising, but friction persists, over 50% of developers reported losing more than 10 hours each week searching for information, onboarding to new code, or toggling between apps.
  |  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.
  |  By Atlassian
AI-native teamwork is here. With your team's context connected via the Teamwork Graph, Rovo moves beyond “answer this” to “take this on” with: Max mode in Rovo Chat that completes complex tasks autonomously (coming soon!) The new, unified builder experience in Rovo Studio is now generally available to put your AI to work. Teamwork Graph-powered agents are now available across your entire stack. New enterprise-grade controls to manage and secure agents at scale.

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.