Atlassian used its Team ’26 user conference this month in Anaheim to explain how its platform has now further evolved to underpin the reality of what the company defines as the AI‑native organization. This still-emerging entity is a company (or indeed a department, an individual team or working group) where human teams are co‑creating alongside agents.
User Base Spread & Reach
While many of the automation advancements coming out of Atlassian will be directed at businesspeople and non-technical staff, an equal and opposite number (give or take) are aligned to serve software engineering teams with agentic automations. The company champions various tools and functions at this level, not least of which is Rovo.
Atlassian Rovo is an AI-powered knowledge discovery tool that connects fragmented data across enterprise apps. It uses a specialized search engine, interactive chat, and autonomous agents to surface insights and automate complex workflows. Inside modern code workshops, developers use Rovo to find documentation, troubleshoot code across repositories, and deploy AI agents to automate repetitive tasks.
Atlassian CEO Mike Cannon-Brookes says that his firm’s customers have one of the richest, most connected context graphs in the world.
“Our Teamwork Graph is not just a database; it’s the connective tissue between people, their work, and their tools. It’s the institutional memory of every project you’ve worked on to date — not only in Atlassian’s apps, across all the connected tools your organization uses. That might include your workflows in Jira, designs in Figma, code in GitHub, people in Workday, and your thinking shared in Confluence or Loom,” said Cannon-Brookes, in his keynote presentation blog at Team ’26.
Building Software, For Software
He reminds us that his organization has spent the last twenty years “building for software teams” in working practice, which means (now that AI is now rewriting the SDLC faster than anything anyone has ever seen) the company’s job is to turn the context software engineering teams already have into an advantage.
An affably disarming Australian with long hair and an occasional gritty turn of phrase that leans on his home nation’s brogue, Cannon-Brookes detailed more of the mechanics of how Atlassian helps coders.
Code Intelligence in Rovo
Teams can assign and track work for Rovo and third‑party coding agents with Agents in Jira. Every agent interaction is auditable, traceable, and governed in Jira, turning “single‑player” prompts into a multiplayer workflow your whole team can see.
Now in early access, Code Intelligence in Rovo lets software engineers and agents ask intent‑level questions across complex, multi‑repository environments, not just “grep for strings” today (see below). By combining a team’s source graph with context from Jira, Confluence, and other locations and tools, Rovo can answer questions like, “Which services still use an outdated UI pattern and who owns the migration plan?” in one place.
What Is Grep For Strings?
In the context of Atlassian Rovo, “grep for strings” refers to its ability to perform deep, literal text matching across an entire enterprise tech stack, much like the classic command-line tool. The grep part denotes the command line search instruction g / re / p – g (Global): search the entire file; re (Regular Expression): the specific pattern or string of text a user is looking for; and p (Print): display the lines that match the pattern on the screen.
With over 150 billion connections, Atlassian says that the Teamwork Graph gives humans and agents the context to search, reason, and act securely across software application development tools and teams.
AI Code Insights
“With all this AI investment, engineering leaders need to understand the ROI. DX, which joined Atlassian last year, now offers an AI experience that tracks AI transformation. With Agent Experience, AI Code Insights, and AI Pulse, teams can see where AI is generating code, how agents are performing, and how they’re impacting productivity and reliability, turning AI from a black box into a measurable, governed part of the SDLC,” stated Cannon-Brookes.
The functions on offer with AI Code Insights include contextual pull request reviews. Unlike standard linters (automated tools that scan code for stylistic inconsistencies, syntax errors and so-called ‘smelly’ code), it checks code against Jira acceptance criteria and Confluence documentation to ensure the code actually does what the ticket asked for.
There’s also proactive issue detection to identify logic errors, security vulnerabilities, and “anti-patterns” (coding habits that cause future problems) before the code is merged — and, finally here, in-line suggestions that don’t just point out problems; they provide specific code snippets and “one-click” fixes to improve readability, maintainability, and performance. The technology can be trained on a team’s specific design systems or logging standards through standard enforcement to ensure every developer follows the same house rules.
Teamwork Graph CLI
“Atlassian is positioning the Teamwork Graph as the context and governance layer for agent work. The CLI and Rovo MCP server give compliant agents a standard read on intent, ownership, and history while admins keep scope and permission control. That puts Atlassian in the running for the agent execution surface for software teams,” said Mitch Ashley, Vice President and Practice Lead, Software Lifecycle Engineering for The Futurum Group.
“Engineering leaders are evaluating where intent, work and authorization converge for agents. Platforms that treat context and governance as separate problems will not survive those evaluations,” added Ashley.
In other DevOps tools, Teamwork Graph CLI is Atlassian’s agent-first command-line interface that gives developers and their AI coding agents direct access to an organization’s Teamwork Graph, while admins retain tight control over scopes and permissions.
MCP‑Compliant Agent
Teamwork Graph tools in Rovo MCP Server give any MCP‑compliant agent, copilot, or automation a standard, secure way to run on your Teamwork Graph, so they act with live ownership, history and relationships.
The overall developer-centric offering from Atlassian continues to strengthen and “developer sessions” signs exist to arrest attendees within the first few yards of stepping into the halls of the Atlassian Team ’26 event. We can expect more of the same in 2026 and beyond – and at a faster and more continuous release cycle by promises laid down by Cannon-Brookes himself.
That’s (as they say in Australia) just about fair dinkum mate!
from DevOps.com https://ift.tt/TrwQsPa
Comments
Post a Comment