Atlassian’s AI Offensive Is Changing Work Forever
Atlassian is reinventing work by deeply embedding AI into its tools, making tasks faster and positioning teams to focus on their activities.
Atlassian has unleashed a sweeping set of upgrades that put artificial intelligence front and center in its platform. If your team relies on Jira, Confluence, or other Atlassian tools, this is more than just a routine update; it marks a fundamental shift in how work gets done. Atlassian’s message is clear: AI is no longer just another feature; it is becoming the very foundation of the user experience in their products.
At the Team ’25 conference in April 2025, Atlassian unveiled a full suite of AI-powered enhancements. The star of these announcements was Rovo, an AI-powered enterprise assistant tightly woven into Atlassian’s ecosystem. Rovo works across Jira, Confluence, and Jira Service Management, and even connects to external tools like Google Drive and SharePoint to bring relevant information into view. By making AI an always-available collaborator in its platform, Atlassian is signaling that the future of teamwork will be heavily augmented by intelligent assistance.
Key AI Moves from Atlassian
-
Rovo goes live for all cloud customers on paid plans at no additional cost. Atlassian is including this AI assistant in Premium and Enterprise subscriptions for Jira, Confluence, and Jira Service Management, removing barriers to adoption.
-
Twenty-plus customizable AI agents arrive to automate routine tasks. These agents can be tailored to use cases ranging from HR onboarding and customer support to DevOps workflows, handling repetitive steps and freeing up teams for higher-value work.
-
New AI-powered Strategy and Teamwork “Collections” roll out. Atlassian introduced two integrated sets of apps, the Teamwork Collection and the Strategy Collection, built as interconnected, AI-native experiences. They aim to connect day-to-day tasks with strategic objectives through real-time updates and context provided by AI.
-
Smarter service management with AI-driven support. In Jira Service Management, Atlassian’s Rovo agents can now suggest actions, answer common questions, and help triage incoming issues. This brings faster resolution and guidance to both IT and business support teams.

AI at the Core of Atlassian’s Strategy
These developments underscore that Atlassian is pivoting to an “AI-first” strategy. Atlassian’s co-founder and CEO, Mike Cannon-Brookes, emphasized that the goal is to generate working solutions, not just small code snippets or isolated outputs. In practice, this means Atlassian tools will increasingly assist in creating complete artifacts: from drafting content in Confluence pages, to building out project plans, and even helping generate code. The company is aligning itself with a broader industry trend of AI-driven application generation, where software is developed with significant help from generative AI.
By infusing generative AI across its platform, Atlassian is preparing for a world where applications can be created or configured with minimal manual coding. Jira and Confluence aren’t just record-keepers anymore; they are becoming intelligent partners that understand context and can propose meaningful changes. This approach has the potential to speed up tasks dramatically. However, to truly realize this vision, Atlassian will eventually need to push the technology beyond assisting with pieces of work and towards producing entire solutions, as the market’s expectations for AI capabilities continue to rise.
The takeaway for users is that AI will soon touch every aspect of project work. From automatically summarizing meeting notes to suggesting test cases or knowledge base articles, Atlassian’s tools will be proactively offering help. It’s a bold move that could redefine how teams collaborate by shifting a lot of the “busy work” over to AI.
Rovo Dev Beta: Playing Catch-Up in AI Development
-
New Rovo Dev suite for software development tasks. Atlassian announced Rovo Dev, a beta toolkit aimed at helping developers with tasks like drafting code plans, generating code, reviewing pull requests, making bulk changes, and simplifying deployments. In essence, Rovo Dev is automating several steps of the software development lifecycle and embedding AI directly into development workflows.
-
Automation vs. innovation. While these features help maintain and improve existing software faster, they highlight that Atlassian’s focus so far is on speeding up individual development steps rather than creating new applications from scratch. Competitors have been quick to offer AI coding assistants that promise to build substantial portions of an app automatically. Atlassian’s cautious rollout suggests it is still refining its approach to true application generation.
-
Market context. Emerging tools like Cursor and Windsurf already integrate advanced AI coding capabilities to reshape how software is built. By comparison, Atlassian’s Rovo Dev beta seems more incremental. Atlassian has introduced a promising set of developer aids, but it may need to accelerate its roadmap to keep pace with leaders in AI-assisted software creation.
-
Room for growth. The limited fanfare around Rovo Dev’s beta release indicates there’s room for Atlassian to further develop and market these capabilities. As the Rovo Dev suite matures, expect Atlassian to broaden its vision from just assisting code maintenance to actually helping generate new applications. For now, the beta is a strong sign of Atlassian’s intentions, but it’s playing catch-up to the rapidly evolving AI development arena.

Teamwork Graph: Harnessing a Unified Work Graph
Atlassian has spent years building what it calls a “Teamwork Graph”, a unified network of data about people, projects, work items, and knowledge that spans Jira, Confluence, and other products. This graph essentially links who is doing what, how work relates to other work, and where knowledge resides in an organization. Now, Atlassian is leveraging this rich connected data to power AI features that deliver context-aware insights and answers.
Imagine asking a question in Confluence and the platform not only finds the answer in a document, but also knows which team was involved and what project it’s part of. That’s the promise of the Teamwork Graph combined with AI: more relevant results and smarter assistance because the system “understands” the relationships between things. Atlassian is even extending this graph to include asset and infrastructure data through new integrations. For example, Atlassian is partnering with tools like Lansweeper to import IT asset information. By doing so, Atlassian could challenge incumbents in IT service management, since a more complete graph of an organization’s technology landscape would rival the configuration databases that products like ServiceNow use.
However, owning and expanding a unified work graph comes with challenges. There’s an ongoing debate about who controls this data and how it’s shared:
-
Access: Will different systems be able to read and write to each other’s graphs, or will Atlassian keep its graph walled off? Companies will need interoperability so that tools can collaborate, but vendors also want to protect their data.
-
Definition: Can everyone agree on what a “project” or a “service” or a “pull request” really means? Aligning these definitions is crucial so that insights aren’t lost in translation when data moves between systems.
-
Governance: Who owns the data in the graph, and under what terms can others access it? This is not just a technical question but a commercial and ethical one, especially as startups and third parties might try to scrape large amounts of information for their own AI analysis.
Atlassian is well aware of these issues. In fact, its leadership has indicated that balancing openness with control of the Teamwork Graph is top of mind. For enterprises, this means there may be negotiations and policies in the future about how your work data can be used by various AI tools. Still, the existence of the graph is a big plus for Atlassian users; it provides the context that AI needs to avoid hallucinations and deliver useful, specific answers instead of generic advice.
Atlassian Expands into Enterprise Service Management
-
Beyond IT: new service templates for business teams. Atlassian is now offering out-of-the-box support portals and workflows for departments like Human Resources, Facilities, and Marketing, not just IT. This means HR can have its own service desk for employee requests, or Marketing can manage creative requests, all using the Jira Service Management platform.
-
Not replacing core systems, but enhancing them. Atlassian isn’t trying to be the next Workday or Salesforce. Instead, these templates sit on top of existing systems of record. For example, an HR team might still use Workday as their primary employee database, but Atlassian’s tools will handle the intake and tracking of employee requests or questions, which Workday alone doesn’t easily manage.
-
The essence of ESM. This approach is a classic enterprise service management strategy, often referred to as ESM. It takes the familiar elements of an IT service desk, such as ticket tracking, standardized workflows, and knowledge bases, and extends them to other business functions. Atlassian’s move validates the ESM trend, acknowledging that every department could benefit from a structured way to handle requests and incidents.
-
Low-code power for every team. Under the hood, Atlassian’s platform now has the low-code/no-code capabilities needed to let non-technical teams customize their own service processes. We anticipate Atlassian will continue rolling out more department-specific solutions, since the infrastructure is in place to support any team that works with requests and queues.
-
Implication for organizations. If you’re already using Jira Service Management in IT, it might be easier now to bring another department on board using Atlassian’s new kits. The benefit is a more unified approach to service across the company, and one less silo to deal with.

Empowering Teams with AI Agents and Rovo Studio
One of the most groundbreaking changes Atlassian introduced is the ability for customers to create and deploy their own AI agents, thanks to Rovo and the new Rovo Studio tool. Previously, advanced AI capabilities were mostly reserved for vendors to build into their products, but Atlassian has now opened the door for its users to experiment with custom “agents” that can act on their behalf within the platform.
What does this mean in practice? If you have a Premium or Enterprise Atlassian Cloud plan, you now have access to Rovo Studio, a no-code interface to design AI agents. These agents could, for instance, monitor a Jira queue and automatically handle certain types of tickets, or scan Confluence to answer common questions without human intervention. Atlassian provides some prebuilt agent templates and has set up default permissions and integration points via the Teamwork Graph to make these agents easier to build and safer to deploy.
It’s important to note that this is new territory for everyone. Atlassian is effectively encouraging “citizen developers” to try their hand at creating AI-driven automations. The company is likely to invest further in helping users succeed. We expect to see more ready-made agents, training modules, and risk management guidelines coming from Atlassian to ensure that these agents are used responsibly and effectively.
At the same time, there are emerging standards and protocols to consider. Atlassian has voiced support for initiatives like the new A2A protocol for agent-to-agent communication, which aims to set rules for how AI agents from different systems might securely talk to each other. There is also discussion around authentication and security standards such as Microsoft’s MCP that need to evolve to support these autonomous agents. Atlassian is managing within the current limitations but knows that broader industry cooperation will be needed to iron out issues like cross-platform agent authentication.
For organizations experimenting with AI agents, a word of caution: you should have governance in place. Just because you can create an agent to automate a task doesn’t always mean you should deploy it to everyone without oversight. It’s wise to start with controlled trials. Define what “good” looks like for an agent’s behavior and have a review process. Some forward-thinking companies, like Shell, have even implemented an internal framework to classify the risk level of automation projects. Adopting a similar model, such as defining tiers of risk based on an AI agent’s potential impact as suggested by the EU’s AI guidelines, can help prevent missteps. The goal is to harness Rovo and custom agents to boost productivity, while avoiding unintended consequences or security issues.
AI-Powered Collections: Game-Changer or Too Much Too Fast?
-
All-in-one teamwork hubs. The new Strategy and Teamwork Collections are essentially packaged work hubs that embed AI into every layer of collaboration. Projects, tasks, documents, and goals are all tied together. Team members from engineering to marketing can see how their work connects to overall strategy in real time. AI plays the role of context provider, surfacing relevant information when you need it and even alerting teams if progress veers off track.
-
Enhanced visibility and alignment. With tools like Rovo and the Teamwork Graph under the hood, these collections give leaders and contributors unprecedented visibility. You can trace a strategic objective down to the user stories in Jira that support it, and see updates instantly. This could greatly enhance alignment, making sure everyone knows why their work matters.
-
Risk of information overload. On the flip side, packing so much functionality into a single experience could overwhelm users. Many teams already feel fatigued by constant pings and data streams. Without proper change management and training, introducing an AI-driven dashboard that’s always updating could lead to confusion or burnout. Atlassian will need to ensure users can tailor notifications and that organizations introduce these tools thoughtfully.
-
Governance of automation. Another potential pitfall is the proliferation of AI agents and automations within these collections. If every team spins up their own agents without oversight, companies might end up with overlapping or contradictory processes. Setting some standards or best practices for creating and managing these automations will be crucial to avoid chaos.
-
Cultural shift still required. While the technology can highlight misalignment or inefficiencies, it can’t resolve deeper cultural or leadership issues. The Collections can show that two departments have conflicting priorities, but it takes human decision-makers to address that conflict. In other words, Atlassian’s new offerings are powerful, but organizations will get the most value from them if they also cultivate a culture of collaboration and clarity.
-
Lock-in considerations. Finally, by leaning so heavily into a one-vendor ecosystem, companies should consider the long-term commitment. The more integrated your workflows become with Atlassian’s AI and data graph, the harder it may be to switch to a different platform down the road. This isn’t necessarily a drawback if Atlassian continues to deliver value, but it’s something to have on the radar when making strategic decisions about adopting these Collections.
Embracing the New AI-Powered Work Reality
Atlassian’s AI offensive marks the beginning of a new era of work management. The “system of work,” which is the combination of all the tools and processes a team uses, is now being infused with AI at every level. Rovo, the enterprise AI assistant, is not just an add-on; it’s becoming the connective tissue linking teams, tools, and goals. By making advanced AI capabilities available by default and at no extra cost on Premium plans, Atlassian is lowering the barrier for organizations to experiment and innovate.
This shift isn’t about replacing humans with robots. It’s about stripping away the drudgery of repetitive tasks so that people can focus on creative, strategic work. Your job won’t be taken by an AI, but the boring parts of it might be. Companies that embrace these changes stand to gain a competitive edge in productivity and agility. Those that ignore or postpone will risk missing out on the benefits as their peers ride this wave of AI-driven efficiency.
Related work.
Rovo
What Atlas Bench does with Atlassian Rovo: scoping what it can reach, defining ownership for agents, and the permission work underneath.
serviceService management
JSM and ESM programs where change control and the system of record for access actually live.
classOnboard to Rovo: Search and chat with AI
A live class on Rovo: beginner, 5 h 30 min, with a hands-on sandbox of your own.
Read next.
Non-Human Identities in Atlassian Cloud: Service Accounts, Tokens, Apps, and Agents
How to govern non-human identities in Atlassian Cloud: service accounts, API tokens, Forge apps, and Rovo agents, each with an owner, scope, and expiry.
October 1, 2026How to Choose an Atlassian Partner for a Jira Cloud Migration
How to choose an Atlassian Solution Partner for a Jira Cloud migration: what to verify, eight questions to ask, red flags, and a shortlist scorecard.
September 30, 2026The Complete Guide to Agent Readiness in Atlassian Cloud
Agent readiness for Atlassian Cloud: the five checks to run before you switch on Rovo agents, from identities and permissions to the off switch.
September 28, 2026How to Review Rovo Agent Access in Jira and Confluence
A step-by-step access review for Rovo agents in Jira and Confluence: who can create them, who can use them, what they can change, and what gets logged.
The blog, weekly.
One email a week with what we published. No drip sequence, and you can leave in a click.
Get an agent readiness assessment
Fixed scope. You get a findings report across identity, platform, and governance, an ownership gap analysis, and a sequenced plan for closing it.
By sending this you agree to our privacy policy.