Confluence Essentials
Confluence Cloud Best Practices
.svg?cb=de4c4813284972f3a2aa9512cc943b23)
Confluence Use Cases
Confluence News
Documentation Guide
#94 - Studio status check before Team ’25 Europe
Patricia Modispacher
In this issue, we take a closer look at Atlassian Studio–what was promised at Team ’25, what has actually been delivered, and what’s still missing.
Back at Team '25 in Anaheim, Atlassian promised something big: Studio. A single place to build agents, automations, and even apps. Six months later, where do we stand? With Team ’25 Europe just around the corner, it’s a good time to take stock: what’s here, what’s still missing, and why it matters.
Why Studio?
Admins and power users have long-faced fragmented automation across Jira, Confluence, and other Atlassian apps. Each tool comes with its own rules, settings, and limits, leading to duplicated effort and disconnected workflows.
Studio addresses this by offering one entry point for agents, automations, and knowledge hubs across the Atlassian ecosystem. In theory, this reduces the need for scripts, plug-ins, or workarounds.
What Is Studio?
Studio is a no-code/low-code platform for creating and managing:
Agents service agents and virtual teammates
Automations with templates or AI support
Assets and hubs to structure and connect knowledge
Apps with Forge — still not available, but announced in at Atlassian Team '25
A Real-Life Example
Before Studio, Atlassian Admins had to jump into Jira to tweak automation rules, then switch to Confluence to adjust page restrictions, and check other products separately. It was easy to lose track of what was running where.
With Studio, you get a single “control center” for all your agents and automations. From one screen, an admin can:
See every automation rule and Rovo agent across Jira and Confluence,
Quickly disable or update them without hunting through multiple products, and
Spot overlaps or conflicting rules before they cause trouble.
Where Studio Stands Today
Atlassian pitched Studio in Atlassian Team '25 as the place where teams could even build their own apps. That vision isn’t fully here yet — app creation with Forge is still on the roadmap. What Studio delivers today is a central hub for agents, automations, and assets. This makes life easier for admins who are tired of jumping between different automation screens. But the real test will be whether Atlassian follows through on the bigger promise: giving builders and creators the same freedom developers currently enjoy to shape Atlassian Cloud.
We’ll be keeping a close eye on what Atlassian shares at Atlassian Team '25 Europe next week. Follow us on LinkedIn for live updates and our take on the news.
Barcelona, here we come!
The countdown is on: Team ’25 Europe kicks off next week, and we’ll be right there in Barcelona!
Stop by Booth #612 to chat about knowledge sharing in Confluence, Jira syncing, and more.
👉 Get a sneak peek what to expect from us at Team.
