Atlassian announced new Jira capabilities for AI-native software development on July 15, 2026, giving engineering teams a way to plan, assign, govern, and measure work across both humans and AI agents. The launch targets a stubborn problem: despite a 65% increase in AI usage, overall developer velocity has plateaued at around a 10-15% gain, a gap that stems from the non-coding parts of software delivery.
The update introduces Teamwork Graph-powered features that turn intent into agent-ready specifications, delegate work to coding agents, monitor agent sessions, automate engineering loops, and track AI spend against output. Jira becomes the system of record where context for agents is a first-class citizen and humans steer, review, and apply judgment.
What AI-native software development requires
Atlassian frames the shift around three practical needs. First, intent must be structured before work begins. An agent needs more than a prompt-it requires requirements, architecture, decision history, and constraints the team already knows. Second, choosing the right agent should not fragment the workflow. A team might use Cursor IDE, Claude Code, a custom cloud agent, and Jira Coding Agent for different tasks, but the process must stay consistent. Third, agent autonomy has to remain observable. Sessions cannot vanish into local terminals with disconnected logs.
When those three conditions are met, agents stop operating as isolated copilots and start participating in the same software development lifecycle as the rest of the team. That is where the Teamwork Graph matters-it acts as a context layer, a living map of work, code, people, decisions, and dependencies that helps agents understand the system around a task, not just the task itself.
Why Jira is the system for this shift
As coding work shifts to agents, they need well-defined tasks with rich, explicit context to deliver high-quality code and manage token costs. Context is rarely in one place. Atlassian built the Teamwork Graph to pull together the atomic task in Jira, requirements in Confluence, conversations in Slack, code context from GitHub, and customer insights from Jira Product Discovery.
Without that context, agents solve tickets too literally, miss architectural constraints, and generate pull requests that look plausible until a senior engineer spends an hour unwinding them. The launch is less about putting more agents in more places and more about giving agents access to the organizational memory teams already rely on. Jira is where that context becomes workflow: intent starts there, agent work gets assigned there, session history is recorded there, and output comes back for review.
New capabilities for agentic development
The features target predictable failure points-vague plans, lossy handoffs, and output teams don't know how to trust. Jira Planner brings spec-driven development into Jira, pulling from codebases and team context to generate structured technical specs in Confluence that are readable by humans and useful to agents. Jira for Slack turns conversations into context-rich work items, and Loom video prompts capture screen actions and voice instructions to generate agent-ready action plans.
Teams can now delegate work directly to Claude Code, Cursor, or GitHub Copilot, with Codex support coming soon. The built-in Jira Coding Agent, included in every paid plan, uses enterprise context and code intelligence to handle routine fixes and return a ready-to-review pull request without a developer switching to a local environment. Agent sessions in Jira give engineers a single view of all coding agents running across spaces and repos, grouped by what needs attention first.
For governance, coding agent automations route routine work-bug fixes, vulnerability remediation, test generation-to agents using Jira's automation rule builder. The Agentic Engineering project template pre-configures workflows, statuses, and integrations. DX AI cost management unifies spend and token data across tools, maps investment to teams and projects, and estimates cost per pull request.
Internal results and a partner perspective
Atlassian ran these patterns with its own engineering teams. Internal benchmarking showed that agents enriched by the Teamwork Graph delivered 44% more accurate results while using 48% fewer tokens than agents without that context. The company also saw reductions in PR cycle time and less time spent on routine tasks.
"The bottleneck in AI-native development isn't agent capability, it's coordination at scale to keep our engineers in the flow. We're partnering with Atlassian to solve that: one place where every agent action is visible, governed, and tied to a business outcome," said Sean Joerg, Deputy CISO & Head of Corporate Engineering at Reddit.
Why this matters for IT and development professionals
For teams already using coding agents, these updates address the coordination overhead that erodes productivity gains. The ability to assign work to agents directly from Jira, monitor their sessions, and tie every action to a business outcome reduces the risk of context loss and review bottlenecks. Engineering leaders get cost visibility across agent tools, not just code output. The message is clear: agents won't remove the need for judgment, but they can operate inside a governed system where humans stay in control.
Your membership also unlocks:
