Atlassian (TEAM) Just Turned Jira Into an AI Coding Command Center

On September 10, Atlassian Corporation (NASDAQ: TEAM ) rolled out a set of tools built around a question most software companies still can't answer well: once you let AI agents loose on a codebase, who is actually watching them? The new capabilities, spanning Jira and Atlassian's DX platform, are meant to give engineering teams a way to hand routine coding work to AI agents while still tracking what those agents touch, whether their output meets internal standards, and whether any of it actually moves delivery forward.

Atlassian's pitch centers on something rivals can't easily copy: institutional context. The company's 2026 AI SDLC study found that 94% of engineering leaders are already using AI, but only 6% have systems in place to scale that work across the full development lifecycle. Atlassian is aiming squarely at that gap. Its new Code Context feature, built on the company's Teamwork Graph, gives Rovo and other coding agents visibility into architecture, requirements, and multi-repository codebases, while Agent Context Controls let platform teams decide exactly which Jira and Confluence spaces those agents are allowed to see. As Atlassian's CTO of AI and Teamwork, Taroon Mandhana, put it, "the biggest bottleneck in AI software engineering isn't model intelligence, it's organizational context." A separate analysis from DX backs that up, finding that teams whose AI tools drew most heavily on Atlassian context shipped roughly 64% more per developer.

The company isn't stopping at context. Agent loops in Jira now scan backlogs for well-defined, unassigned tickets, hand them to Jira's coding agent for execution and testing, and open pull requests ready for human review. A new Standards feature lets platform teams set coding rules once and apply them everywhere agents work, and a dedicated AI reviewer checks pull requests against those rules before code ships. Together, it looks less like a chatbot bolted onto Jira and more like an attempt to build an assembly line for agent-written code.

Still, the same study Atlassian used to sell these tools also describes the size of the problem it's trying to solve. If only 6% of engineering leaders currently have systems capable of scaling AI work, adoption of a new governance and measurement layer is far from guaranteed, no matter how well it's designed. Getting large, change-averse engineering organizations to actually run on agent loops tends to take longer than a product launch implies.