Session catalogue

The future of software development isn’t just about smarter tools — it’s about seamless collaboration between them. In this session, we’ll explore how Atlassian’s Rovo Dev suite, including its latest beta features, creates a unified, intelligent layer across the entire SDLC. From code generation and review in your IDE, to automated troubleshooting in Bitbucket pipelines, to context-aware actions in Jira and beyond, Rovo Dev’s agents don’t just work in isolation — they amplify each other’s strengths.

Rovo Dev IDE extension, CLI, Code Reviewer, Pipeline Troubleshooter, Jira integration, and automation features interconnect together to deliver a developer experience that’s more than the sum of its parts. We'll run real-use cases where Rovo Dev shares context, automates handoffs, and surfaces insights at the right moment, reducing friction and boosting software quality.

We'll demonstrate how you can leverage Rovo Dev’s ecosystem to eliminate silos, accelerate delivery, and ensure every step of your SDLC is informed by the full context of your work.

At Atlassian, we've transformed our engineering practices by integrating AI throughout our development lifecycle, from ideation to deployment. Our engineers leverage our own products like Rovo Dev to accelerate code development, automate repetitive tasks, and reduce toil. 

We'll share real-world examples from our engineering teams, demonstrating how AI assists in code generation, code review, automated testing, documentation, and releases. Whether you're looking to introduce AI into your development workflow or further optimize your practices, this session provides actionable insights from the journey of thousands of engineers here at Atlassian.

Join us to discover how your team can leverage similar approaches to build smarter, ship faster, and drive more business impact by adopting AI effectively.

In this session, we will step back from the individual modules and labs of Day 1 to connect the dots and return to the big picture: Rovo Dev as the foundation of an AI‑native SDLC.

We will:

• Revisit the core concepts introduced today - Rovo Dev as a context‑aware AI teammate that spans planning, coding, review, and deployment
• Walk through how the different surfaces you explored (CLI, IDE, Code Review) come together as one cohesive experience rather than isolated AI tools
• Highlight the key patterns from today’s exercises that distinguish “AI‑assisted development” from a truly AI‑native software delivery lifecycle
• Tie today’s learnings back to Atlassian’s broader vision for Rovo Dev and preview how upcoming sessions will deepen these capabilities across issues, repositories, and pipelines

By the end of this session, you’ll have a clear mental model of how the concepts from Day 1 fit together, how Rovo Dev reimagines the SDLC end‑to‑end, and what to look for in the rest of the track as you design your own AI‑native development workflows.

Engineers spend countless hours on repetitive, mundane tasks such as resolving security vulnerabilities, migrations, and busy work that drains productivity. What if you could automate it all?

Rovo Dev for Jira is the must-have tool for engineering teams already planning their work in Jira. With deep integration across all Atlassian products and third-party tools connected to your cloud organization, Rovo Dev understands your team, your codebase, and your organization's unique needs. Join us to discover how your team can reclaim thousands of hours — and focus on what really matters.

Key takeaways:

• Get up and running with Rovo Dev in minutes
• Create custom prompts your team can reuse and share
• Automate away the busywork

Writing code doesn't have to mean leaving your development environment. With Rovo Dev CLI, you can work naturally in your terminal or IDE while your AI agent understands the full context of your work — your Jira issues, Confluence documentation, code patterns, and team knowledge.
Unlike generic AI coding assistants that treat every codebase as a blank slate, Rovo Dev CLI is built for teams already using Atlassian tools. It integrates directly with your Jira projects and Confluence spaces, so your agent can:

• Access your work context
• Retrieve Jira issues, search for related tasks, and understand project requirements without manual context-switching
• Leverage team knowledge
• Find relevant Confluence documentation, architectural decisions, and best practices that are already documented in your space (Work in your workspace)
• Maintain your workflow with support for sessions, custom prompts, memory files, and persistent configuration
• Stay in control
• Configure granular tool permissions, use shadow mode for safe experimentation, and review changes before they're applied

Whether you're tackling a complex feature, reviewing pull requests, or exploring an unfamiliar codebase, Rovo Dev CLI brings the intelligence of an AI agent directly to where you code — without forcing you to adopt new tools or workflows. In this talk, we'll explore how Rovo Dev CLI's deep Atlassian integration transforms the coding experience, allowing teams to code more naturally and efficiently while staying connected to the context that matters.

AI is transforming how teams work and Atlassian’s developer platform is evolving with it. In this session, we’ll explore how Forge is becoming the foundation for building, integrating, and extending AI-powered experiences across the Atlassian platform.

You’ll get alook at new capabilities that let you build agents, define “skills,” and leverage large language models in your apps.

We’ll dive deep into how developers can:

• Use Forge LLMs to integrate high-quality, eval-tested AI features — with tips for cost control, usage management, and safe programmatic access.
• Provide “Skills” to power Rovo agents in Atlassian Studio, giving customers a smarter way to interact with your app functionality 
• Integrate remote agents with Rovo and Jira using A2A and Forge
• Get a sneak peek at upcoming features that enable richer, multi-step, and autonomous agents built natively on Forge.

Throughout the talk, we’ll demo working examples that show how Marketplace partners and customer developers can turn today’s AI prototypes into production-ready experiences.

Whether you’re an experienced Forge developer or new to building AI features, this session will give you practical techniques, architectural insights, and a roadmap for where the Atlassian AI platform is headed next.

What if you could instantly surface every open bug in your Jira project, spin up a Confluence page with technical specs for your next big idea, or bulk-create Compass components—all without ever leaving your favourite AI interface? With the Atlassian Rovo MCP server, this isn’t just possible—it’s happening right now.

In this session, you’ll discover how the Rovo MCP server empowers developers, team leads, and technical practitioners to unlock Atlassian’s full potential from wherever they work, be it Cursor, OpenAI ChatGPT, GitHub Copilot, or beyond. We’ll explore real-world examples of how anyone can use MCP’s powerful tools, like Rovo search and fetch, to automate tasks, surface insights, and boost team collaboration.

Don’t miss your chance to get ahead of the curve: we’ll also reveal what’s next on the MCP roadmap, including the upcoming ability to add custom Rovo skills as callable tools. Whether you’re building for your team or your customers, this session will equip you to harness the next generation of AI-powered productivity in the Atlassian ecosystem.

Key takeaways:

• Discover how the Atlassian Rovo MCP server enables seamless AI-powered workflows across Jira, Confluence, Compass, and more.
• Learn actionable strategies for integrating AI and automation into your software development lifecycle.
• Get an exclusive preview of upcoming features, like custom Rovo skills.

In this session, we will explore how Rovo Dev extends beyond coding assistance to become a powerful partner in code review and automation. Building on the CLI and IDE workflows from earlier in the day, we’ll show how Rovo Dev steps into your existing Bitbucket and GitHub workflows as a context-aware first reviewer and an engine for automating repetitive SDLC tasks.

We will:

• Walk through how Rovo Dev reviews pull requests in Bitbucket and GitHub, checking against acceptance criteria, surfacing potential issues, and suggesting concrete improvements
• Show how Rovo Dev uses pipeline and repository context to help diagnose build failures and reduce back-and-forth during review
• Highlight common automation patterns - from feature flag clean-up and dependency updates to code quality fixes - that free developers from repetitive work
• Connect these capabilities back to the broader AI‑native SDLC vision: using an AI agent to continuously enforce quality and keep code moving from review to deploy with less friction

By the end of this session, attendees will understand how Rovo Dev fits into their existing PR and automation flows, and how it can help teams ship safer, cleaner code without slowing down delivery.

This mini lab offers a guided, hands-on introduction to Rovo Dev in Jira, focused on how an AI teammate can support modern software planning and coordination.

Participants will experiment with Rovo Dev in real Jira contexts — seeing how it interprets work, brings in relevant code and pipeline signals, and helps clarify what’s happening in a project. The exercises are designed to give a feel for how Rovo Dev can simplify day-to-day workflows in Jira, from understanding the state of work to staying aligned across issues, epics, and teams.

By the end of the lab, attendees will have an intuitive sense of what it’s like to work with Rovo Dev directly in Jira, and how this fits into an AI‑native SDLC without requiring teams to overhaul their existing practices.

In this mini lab, you will get hands-on experience using Rovo Dev for code review and automation in real-world scenarios. Guided by Jovana and Bryan, you’ll work through a set of practical exercises designed to mirror how development teams use Rovo Dev day-to-day.

You will:

• Connect Rovo Dev to a sample repository in Bitbucket or GitHub and trigger AI-powered code reviews on pull requests
• Interpret and act on Rovo Dev’s review feedback, iterating on changes and seeing how it tracks acceptance criteria and code quality concerns
• Configure simple automation flows to handle repetitive work — such as cleaning up feature flags or updating dependencies — so Rovo Dev can open and update PRs on your behalf
• Experience how code review and automation tie back to the AI‑native SDLC story: the same agent that helps you write code can also help you review, maintain, and continuously improve it

Attendees should leave this lab with a concrete feel for what “AI in the loop” looks like at review time, and clear ideas for how to bring these patterns back to their own Bitbucket/GitHub and automation setups.

The Forge runtime is the engine for a new generation of marketplace apps, but tackling compute-heavy tasks often feels quite daunting. This session is for every developer who wants to get more out of those precious GB-seconds on the Forge runtime. We'll look at the real-life example of how we added Optical Character Recognition (OCR) to a production app and how developers can use WASM to speed up computation on Forge.

This is a performance session built on our own production experience: How we built it, what went well, what did not go well at all, and what we would not do again. Attendees will walk away with a proven roadmap for identifying, benchmarking, and implementing WASM to solve high-performance challenges, allowing them to get the most out of Forge's runtime.

Key takeaways:

• A practical roadmap for running complex WASM modules within a Forge function
• Decision framework for identifying when WASM is necessary for high-performance tasks

Since 2016, codefortynine has built 13 Connect apps that together exceeded 20,000 installs and served 2.5+ million users across 150+ countries. When Atlassian accelerated the move to Forge, we committed to migrating our largest Connect apps in just six months — without degrading reliability or customer value.

In this session, we share concrete, anonymized migration metrics (e.g., commits, hours, # of ECOHELP tickets, etc.) and the decisions that made the biggest impact. We’ll cover how we navigated Forge limitations (request timeouts, response sizes, resource ceilings), what we did when previously used Connect modules were unavailable, and the architecture & operations patterns that kept us shipping confidently.

It’s a constructive, data-backed playbook from an Atlassian Platinum Marketplace Partner. You’ll leave with realistic benchmarks, reusable engineering patterns, and a practical checklist to de-risk your own Connect-to-Forge journey in 2026.

Key takeaways:

• Realistic effort ranges for migrating sizable Connect apps to Forge — benchmarks for commits, person-hours, tickets, and releases.
• Reusable engineering patterns for Forge constraints.
• Bridging module gaps when a previously used Connect module isn’t available in Forge — UX adjustments, smart API combinations, and other shortcuts. 

The Atlassian Forge UI kit offers a robust foundation for building apps, but sometimes you want your creations to reflect your team’s unique style or add a spark of delight for your users. In this session, we’ll explore how Forge and React can help you move beyond the basics, empowering you to craft apps that are not only functional but also visually engaging and memorable. Whether you’re aiming for a polished, branded experience or simply want to experiment with new UI ideas, custom styling opens up a world of creative possibilities.

Through a live “before and after” demo, I’ll walk you through the process of transforming a standard Forge app into something that stands out. Along the way, I’ll share practical insights, lessons learned, and approaches for customizing the look and feel of your apps. This talk is designed for developers and designers alike, offering inspiration and actionable ideas to help you bring more personality and polish to your next Forge project.

Key takeaways:

• Discover practical approaches for customizing the appearance of Forge apps using React, while respecting Atlassian’s design principles
• Learn how to identify opportunities for creative UI enhancements that improve user experience and engagement
• Gain inspiration and confidence to experiment with styling in your own Forge projects, regardless of your prior design experience

Learn about the Forge MCP (Model Context Protocol) and how it helps developers build better AI-powered apps on the Atlassian platform. The MCP is a way for AI tools — like code assistants or Rovo Agents — to get accurate information about Forge projects, modules, and settings. It helps your AI understand Forge instead of guessing how things work — like giving a llama a proper map before it wanders off into the paddock. It still does the walking, but now it knows where the gate is.

See how to set up and use the Forge MCP with a short demo that brings it all to life. The example will highlight how the MCP keeps AI grounded in real Forge documentation and helps it generate smarter, more useful results. Whether you’re experimenting with Rovo, building automations, or exploring new AI workflows, this session will give you a solid foundation to start.

By the end, you’ll know what the MCP does, how to use it in your own development, and how it can help you and your AI teammate work together with confidence.

Key takeaways:

• What the Forge MCP is and why it makes AI tools smarter about Forge
• How to connect and use the Forge MCP in your own environment
• How the MCP can help AI agents build better Forge apps safely and accurately

In today’s hybrid world, collaboration data is scattered across countless tools — Jira, Confluence, Slack, Google Workspace, Notion, and beyond. While each system holds valuable insights, none provides the whole picture of how teams actually work.

Pio Software’s Teamwork Graph Connectors unify these fragmented data sources into a cohesive knowledge graph, mapping relationships between teams, projects, and information across platforms.

This talk is relevant for every Atlassian builder facing integration chaos. It’s unique because it goes beyond APIs — showcasing how to architect meaningful cross-tool intelligence that powers automation, analytics, and AI-driven insights within Atlassian Cloud.

Key takeaways:

• A blueprint for building scalable cross-product data integrations using Atlassian Forge and external Graph APIs (Github, Microsoft, etc.)
• Real examples of how Teamwork Graph Connectors make it possible to visualize team relationships across Jira, Confluence, and third-party systems
• Best practices for syncing identity, context, and work items across tools without compromising data privacy
• Hands-on inspiration to build smarter Atlassian apps — ones that understand the organization’s work graph, not just process its tickets

This session targets:

• Developers & solution architects building integrations or analytics on top of Atlassian Cloud.
• Atlassian Marketplace partners exploring ways to enrich their apps with external intelligence.
• Enterprise admins & data engineers who manage complex hybrid toolchains.

Have you ever imagined a feature that would take your team’s Jira or Confluence experience to the next level? Atlassian’s platform is designed for flexibility, and with Forge, you have the power to bring your most creative ideas to life. In this lightning talk, I’ll show how Forge makes it possible for anyone, from newcomers to seasoned developers, to quickly turn those “wouldn’t it be cool if…” moments into real, working features.

We’ll walk through the process of transforming an idea into a live app using the Forge CLI, custom UI with React, and Atlassian’s APIs. Along the way, I’ll share practical tips, set up shortcuts, and the “aha!” moments I discovered as I dove into Forge for the first time. Whether you’re looking to streamline workflows, delight your users, or simply experiment with new possibilities, this session will give you the tools and confidence to start building right away.

Key takeaways:

• Learn how to use the Forge CLI, React, and Atlassian APIs to rapidly prototype and deploy custom features for Jira or Confluence
• Discover practical tips and shortcuts for getting started with Forge, even if you’re new to the platform
• Walk away with a clear, step-by-step approach and code snippets to help you build your own wishlist features

Keeping apps up to date in the cloud is harder than it should be. Developers struggle with version fragmentation, supporting multiple outdated versions, and feeling helpless trying to get Admins to press that update button. Admins, in turn, lack the awareness, tools and information to confidently manage updates, leading to security risks, missed features, and a slow pace of innovation.

In this session, we’ll unveil Atlassian’s new approach to app versioning and delivery: rolling releases and features. By decoupling permissions from versions and introducing feature-based approvals, we’re making it easier for developers to ship new features and for admins to maintain secure, up-to-date environments. We’ll share real-world challenges app developers currently face, how they can be overcome, and practical strategies for adopting these changes in your own apps.

Whether you’re a developer tired of supporting legacy versions, or too afraid to ship new features in your existing app, or an admin seeking more control and transparency, this talk will show you how Atlassian is transforming Forge app delivery for the cloud era.

Forge Containers is here! We're unlocking new possibilities for apps that need custom runtimes, native dependencies, or more control over execution environments. In this session, we’ll officially open the doors to public early access, giving developers their first opportunity to get hands-on with this long-awaited capability.

We’ll take you behind the scenes of how Forge Containers was built: from the architectural design that powers secure, scalable containerized app execution, to the lessons learned along the way. You’ll see live demonstrations of how to use containers in your own Forge apps, hear early success stories from partners who’ve been testing it in private preview, and get a look at what’s coming next as we continue to evolve the capability.

Whether you’re building data-intensive apps, integrating third-party libraries, or just curious about how Forge is growing to meet the next wave of developer needs, this session will give you the context, knowledge, and inspiration you need to start building with Forge Containers during Atlas Camp’s hands-on workshops.

In this session, we’ll explore two complementary approaches to understanding Forge SQL performance: profiling slow queries and diagnosing failed ones. First, we’ll see how to use dbExecutionTime to aggregate total database execution time across a single invocation, helping developers detect performance regressions and, when needed, inspect execution plans for individual queries once latency thresholds are exceeded.

Then, we’ll focus on automating the analysis of failed queries, such as those that return: “Your query has been cancelled due to exceeding the allowed memory limit for a single SQL query.” or “The provided query timed out from database.”

You’ll learn how to automatically detect these errors by inspecting their SQL error codes, trigger follow-up queries to Forge SQL metadata tables, and retrieve the corresponding execution plans — all within the same resolver invocation.

This approach enables your app to automatically collect and log diagnostic details for failed queries — even in Forge’s isolated database environment, where direct database access isn’t available.

Finally, we’ll discuss practical optimization strategies — from query rewrites to using @forge/kvs for caching — to improve app performance even when queries can’t be further optimized.

Key takeaways:

• Use dbExecutionTime to measure total database time per invocation and detect performance regressions
• Automatically analyze timeouts and out-of-memory errors by fetching execution plans from metadata tables
• Apply practical optimizations, including caching query results with @forge/kvs, to improve stability when query tuning isn’t enough
   

Building a full-featured, UX-heavy Connect app on Forge has long been seen as nearly impossible. Refined Sites, one of the most design- and performance-intensive apps on the Atlassian Marketplace, set out to challenge that assumption. Through close collaboration with Atlassian’s Forge team, we’ve pushed the boundaries of what’s possible on Forge, running a full-page front end, backend services in Forge containers, and storing content in Forge SQL & Forge Object Store.

Ever wished you could peek under the hood of your Forge app (while it’s running) and fix things on the fly? Traditional debugging tools live outside your application, forcing you to jump between logs, dashboards, and backend scripts. At Elements, we wanted a faster, more integrated way to understand what happens inside our Forge apps as they run.

In this session, we’ll show how we built a developer-mode debug tool for Forge apps that any team can adapt using an extensible architecture. You’ll see how modular UI components, reusable resolvers, and a structured layout enable safe in-app data inspection and live testing without leaving the app.

Whether you’re building internal tools or large-scale Marketplace apps, you’ll take away patterns for embedding observability and debugging directly into your own Forge experiences — enabling faster iteration and a deeper understanding of how your apps behave.

Key takeaways:

• Discover and see in action the real power of Elements Forge DevTools — a demo showing how we use it to relaunch Forge functions, inspect resolver data, manipulate stored data, and validate computations directly inside a Forge app
• Learn how we built it — from designing reusable Forge UI components to managing resolver calls and app state between the host and debug panel
• Hear what worked (and what surprised us) — lessons learned from experimenting with context handling, performance, and maintainability while building the tool