Get more out of your existing Atlassian investment with new AI capabilities, automation, and platform integrations: At “Team ’26” on May 6, 2026, Atlassian announced a wave of platform updates that expand what existing Jira, Confluence, Loom, and Jira Service Management subscriptions can do, with new artificial intelligence (AI) capabilities, deeper integrations, and broader governance controls.
Summary
- Atlassian has expanded the Teamwork Graph with a new Command Line Interface (CLI), Model Context Protocol (MCP) Server tools, and generally available Forge connectors. That makes Atlassian context available to AI assistants and developer pipelines beyond the Atlassian user interface.
- Atlassian extended Rovo, its AI experience, with a new Max reasoning mode (coming soon in early access), context-aware search, and stronger administrator governance over agents and AI credit consumption.
- The new Rovo Studio building experience is now generally available. It lets teams build agents, no-code automations, and custom Forge applications from natural-language prompts.
- Teamwork Collection now includes generally available agents in Jira, third-party agents in Confluence (open beta), Remix with Rovo and Confluence slides (beta), and a redesigned bug-reporting workflow that connects Loom and Jira.
- Strategy Collection adds Strategic Intelligence and Funds in Focus, Human & AI Capital Management in Talent, and live Strategic Planning in Focus. This turns the bundle into a real-time executive operating model.
- New partner integrations for Jira Service Management AIOps with Lansweeper, Coralogix, and Honeycomb expand the existing ecosystem with New Relic and Dynatrace.
What is changing?
At Team ’26 in Anaheim, Atlassian announced a broad set of platform updates that expand Teamwork Graph, Rovo, Rovo Studio, the Teamwork Collection, the Strategy Collection, and the AIOps partner ecosystem. The common theme is to embed AI deeper into existing Atlassian products and to open up the underlying context layer to third-party tools, so customers can do more with the licenses they already have.
These updates apply across Atlassian Cloud and, where indicated, Data Center. Most capabilities are delivered through the existing subscription model. AI consumption is metered through Rovo credits, which customers can purchase as a separate add-on to their current plans.
Teamwork Graph
Teamwork Graph is Atlassian’s context layer that connects people, work items, code, and content across Atlassian and connected applications. AI agents read from the graph to get context and write back to it as work progresses, so the same context is available regardless of which product a user is working in.
- The new Teamwork Graph Command Line Interface (CLI) is in open beta and lets developers query the graph from terminals and Continuous Integration / Continuous Deployment (CI/CD) pipelines. Graph context becomes available outside the Atlassian user interface.
- The new Teamwork Graph tools in Rovo Model Context Protocol (MCP) Server are also in open beta and expose graph context to any MCP-compatible AI assistant. Customers can use third-party tools without losing Atlassian context.
- Custom Teamwork Graph Connectors via Forge are now generally available. Customers can build their own connectors to bring data from proprietary or legacy systems into the graph while keeping existing permissions intact.
Rovo
Rovo is Atlassian’s AI experience and is licensed through Rovo credits, available as a subscription add-on to existing Atlassian plans. Rovo credits are consumed when agents, search, or generative actions run, so the cost scales with actual usage rather than seat count.
- The new Max reasoning mode in Rovo Chat (coming soon in early access) plans and executes multi-step tasks across connected tools and then reports back. This reduces the amount of manual coordination required for longer workflows.
- Rovo Search now pulls live context from connected tools based on the application the user is currently in, so search results are tailored to the active task rather than being generic.
- New agent and credit governance views give administrators visibility into which agents exist, who built them, where they run, and how Rovo credits are consumed. That is essential for predictable AI cost management.
- Administrators can now separate AI access permissions from agent-building permissions. Broad AI usage can be enabled without giving every user the ability to create new agents.
Rovo Studio
The new Rovo Studio building experience is now generally available. It is a unified workspace where anyone (not just developers) can describe a problem in natural language and have Studio assemble a working solution from existing platform components. This lowers the barrier for non-developer teams to automate their own workflows.
- Studio-built agents can be configured with their own tools, skills, and knowledge sources, and connect to external tools through the open Model Context Protocol (MCP) standard.
- Studio-built automations run across Jira, Confluence, Jira Service Management, and connected applications without requiring any code, and inherit the permissions of the user who built them.
- Custom Forge applications can be generated from a single prompt, scaffolded and previewed in Studio, and shipped with roles, approvals, versioning, and audit trails built in — which keeps shadow AI risk under control.
Studio-built agents run on Rovo credits, so the licensing impact scales with how often agents are actually used rather than with the number of agents that have been built.
Teamwork Collection
The Teamwork Collection bundles Jira, Confluence, and Loom with Rovo capabilities embedded directly inside each product, so users do not need to switch tools to access AI features.
- Agents in Jira are now generally available and can take ownership of work items, including assignment and code updates, with a full audit trail of every action they take.
- Third-party agents in Confluence are in open beta. Users can mention agents from Lovable, Replit, Databricks, and Gamma directly on a Confluence page the same way they would tag a colleague.
- Remix with Rovo (beta) converts written content on a Confluence page into charts, timelines, infographics, and other visual formats without changing the original source.
- Confluence slides (beta) generates AI-built presentations from Confluence content and supports presenting directly from within Confluence.
- Create with Rovo in Jira (beta) turns documents, meeting summaries, and email threads into structured Jira work items automatically, removing a lot of manual ticket creation.
- Agent briefings in Loom (coming soon) record a walkthrough and convert it into a structured prompt that agents can act on. This is useful for visual or interface-related tasks that are hard to describe in text.
- Bug reporting with Loom and Jira is now generally available and captures device, console, and network data automatically, then assigns the draft fix to Rovo Dev.
Strategy Collection
The Strategy Collection is Atlassian’s leadership-focused offering, built on Focus, Talent, Align, and Rovo. It enriches the Teamwork Graph with priorities, funds, teams, and systems data so leaders can monitor strategy execution in one place rather than reconciling separate status reports. At Team ’26, Atlassian announced three new capabilities that turn the bundle into a live executive operating model:
- Strategic Intelligence in Focus enters open beta in June 2026 and surfaces what is on track, what is at risk, and what needs a decision today. Every signal is generated by a Rovo agent reasoning over the Teamwork Graph and the priorities the leader chose to monitor.
- Funds in Focus (generally available in June 2026) places budget, costs, benefits, and forecast versus actuals alongside strategic health information, so financial performance and delivery health live in the same view.
- Human and AI Capital Management (coming soon) identifies the skills already present in your workforce by looking at the work people actually do. It also shows how much AI is being used and what it costs, broken down by team and by strategic priority.
- Strategic Planning in Focus enters its Early Access Program (EAP) before June 2026, with general availability rolling out through the rest of the year. Strategic Planning keeps the plan live so reallocation decisions reach affected teams the same day.
Lansweeper, Coralogix & Honeycomb integrations in Jira Service Management
Atlassian has added three new partner tools to Jira Service Management AIOps. They join New Relic and Dynatrace in the existing partner ecosystem. All five share data with Jira Service Management through Atlassian’s remote MCP server, so support teams see what they need without switching between systems when something goes wrong.
- Lansweeper brings asset discovery (hardware, software, and dependencies across on-premises and cloud environments) directly into incidents and change requests, so responders can assess impact and plan changes without leaving the ticket.
- Coralogix brings full-stack observability (logs, metrics, traces, and security events) into the incident view, with AI-driven root cause analysis (beta) and automated post-incident reviews in Confluence.
- Honeycomb brings high-cardinality debugging into Jira Service Management for complex, microservices-heavy systems, with AI-assisted root cause suggestions (beta) and post-incident reports that include Service Level Objective (SLO) impact.
Customer benefits
- Customers get more value from existing licenses because most of the updates apply to current Jira, Confluence, Loom, and Jira Service Management subscriptions without requiring a new product purchase.
- Teams can automate routine work without code through Rovo Studio, which reduces the dependency on developer capacity for everyday process improvements.
- Administrators gain central governance over AI usage, with visibility into agents, credit consumption, and access permissions across the entire Atlassian platform.
- Service teams handle incidents faster through context-rich AIOps integrations that bring asset, observability, and debugging data into the same view as the incident itself.
- Leadership teams can connect strategy to live work data through the Strategy Collection, which removes the lag between status reporting and the reality on the ground.
What organizations should do now
- Review current Atlassian subscriptions, user counts, and product mix to identify which of the new platform capabilities are already covered by existing entitlements.
- Assess whether Rovo credits should be added to the next renewal, and model expected consumption based on the agents, search, and generative actions teams plan to use.
- Update internal AI governance, including agent inventory, credit caps per team, and access permissions, before opening Rovo Studio more broadly inside the organization.
- Plan adoption windows around the published Early Access Program (EAP) and general availability timelines for the Strategy Collection and Rovo features that are still in beta.
- Engage an independent licensing advisor like SCHNEIDER IT MANAGEMENT before signing or renewing, so the renewal reflects the new capabilities and integration scope rather than last year’s product mix.
Ready to get more out of your Atlassian investment?
Our Atlassian licensing experts save costs while boosting productivity for you. Contact us to optimize your Atlassian licensing.
More information
Jira Service Management integrations: https://www.atlassian.com/blog/jira-service-management/introducing-new-aiops-integrations-with-lansweeper-coralogix-and-honeycomb.
Teamwork Graph changes: https://www.atlassian.com/blog/company-news/teamwork-graph-team-26.
Rovo changes: https://www.atlassian.com/blog/company-news/rovo-team-26.
Teamwork Collection changes: https://www.atlassian.com/blog/company-news/built-for-the-next-era-of-teamwork-whats-new-in-teamwork-collection.
Strategy Collection changes: https://www.atlassian.com/blog/company-news/strategy-collection-team-26.
Atlassian partner page: https://www.schneider.im/software/atlassian/.