Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

Bitbucket Pipelines lets you build reusable pipelines and share them across repositories. These reusable, shared pipelines need a way to share artifacts. Otherwise, we’ll have to repeat expensive steps such as downloading and installing dependencies and building the application code. You can now specify an artifacts section for child pipelines, with upload and download keywords. Artifacts listed under upload will be moved from the parent pipeline into the child pipeline, where they can be used and potentially modified.

Building and maintaining a 2000+ line bitbucket-pipelines.yml can be a lot of work. Now you can split large bitbucket-pipelines.yml files into multiple, smaller pipelines.yml files. These smaller files can be composed via shared pipeline syntax to replicate the functionality of the original bitbucket-pipelines.yml file. They can also be shared with and reused in other repositories.