Atlassian launches AI-native software development system in Jira
Atlassian Corporation introduced new Jira capabilities to advance AI-native software development, utilizing the Teamwork Graph to provide enterprise context. The system improves agent accuracy by 44% and reduces token usage by 48%, addressing a productivity gap where AI usage has risen 65% but velocity gains are only 10%. Features include Jira Planner, Loom video prompts, and integrations with Claude Code, Cursor, and GitHub Copilot.

*this image is generated using AI for illustrative purposes only.
Atlassian Corporation today announced new capabilities in Jira designed to advance AI-native software development for engineering organizations. The launch addresses a widening productivity gap where AI usage by engineers has increased by 65%, yet developer velocity gains remain at approximately 10%. The new system provides a single place to plan, orchestrate, and scale agentic work across the full software development lifecycle.
The core of the update is the Atlassian Teamwork Graph, which connects work, teams, goals, code, and knowledge across the software development lifecycle (SDLC). By providing this enterprise context, agents can act with greater relevance. In internal benchmarking, agents enriched by Teamwork Graph showed 44% more accurate results while using 48% fewer tokens than agents operating without that context.
Accelerating Planning and Spec-Definition
The new capabilities help teams turn conversations, requirements, and codebase context into work agents can understand. Jira for Slack allows users to turn conversations into context-rich specs and kick off agent tasks by asking @Jira. The all-new Jira Planner pulls from the Teamwork Graph to define requirements and generate a structured technical spec in Confluence. Additionally, Loom now turns screen recordings and voice instructions into structured action plans that agents can execute.
Delegating and Monitoring Agent Work
Jira now serves as the single source of truth for coding agents, whether execution happens inside Jira, in a cloud agent, or locally. Users can assign work items directly to Claude Code, Cursor, or GitHub Copilot from Jira. The built-in Jira Coding Agent, included in every paid plan, uses Teamwork Graph context to turn work items into ready-to-review pull requests. A new unified view provides visibility into agent sessions across spaces and repos.
Enterprise Deployment and Measurement
To support enterprise adoption, Atlassian introduced autonomous workflows in Jira's automation rule builder. Teams can automate bug fixes, vulnerability remediation, test generation, and documentation updates. A new Agentic Engineering project template helps teams stand up agent-ready projects with pre-configured workflows. Furthermore, the DX AI cost management report unifies spend and token data across third-party tools to calculate an estimated cost per pull request.
Availability and Key Metrics
| Feature | Availability | Key Metric/Benefit |
|---|---|---|
| Teamwork Graph | Available now | 44% more accurate results, 48% fewer tokens |
| Jira for Slack | Available now | Turns conversations into specs |
| Jira Coding Agent | Available now | Ready-to-review pull requests |
| Jira Planner | EAP Waitlist | Generates structured technical specs |
| DX AI Cost Management | Atlassian DX customers | Calculates cost per PR |
How will the integration of third-party coding agents like Claude Code and GitHub Copilot impact Atlassian's partnerships with competing cloud providers?
What specific enterprise security measures are being implemented to manage autonomous workflows for vulnerability remediation?
How might the introduction of the DX AI cost management report influence customer pricing strategies for third-party AI tools?



























