AIToday

Atlassian expands Jira to orchestrate developers and AI agents

SiliconANGLE AI4h ago
Atlassian expands Jira to orchestrate developers and AI agents

Key takeaway

Atlassian has expanded Jira to help teams manage work performed by AI agents alongside developers. The new features include automated workflows that assign tasks to agents, integrations with third-party coding agents, and a template for advanced users. This responds to the reality that while AI coding tools are widely adopted, companies struggle to realize return on investment—with research showing AI agent code is accepted less frequently than human code and tends to be simpler in structure.

Summaries like this, in your inbox every morning.

Sign up free →

3 Key Points

  • What happened

    Atlassian announced updates to Jira including a new Jira Planner to turn project ideas into technical specifications, a Jira Coding Agent, and integrations with third-party agents. The company added an Agentic Engineering Template and automation rules so agents can be automatically assigned work as issues move through the board.

  • Why it matters

    Coding-agent adoption is widespread, but planning and coordination have become a bottleneck. Atlassian is positioning Jira as a control plane for mixed teams of developers and agents—addressing the 'work that surrounds work' (unclear requirements, handoffs, documentation, governance) that slows AI productivity. Research shows AI agents are accepted less frequently than human code and tend to be structurally simpler, so better coordination and context are critical.

  • What to watch

    Jira Coding Agent handles bounded work directly from the platform without requiring a coding editor. Developers can also assign tasks to other agents including Claude, Cursor, GitHub Copilot, and others, keeping work grounded in Jira's project history and context.

In Depth

Atlassian announced a suite of updates to Jira designed to position it as an orchestration hub for mixed teams of human developers and AI agents. The updates include three main components: Jira Planner, which transforms incomplete project ideas into technical specifications; Jira Coding Agent, which can be triggered directly from Jira to handle bounded work in the cloud; and integrations with third-party agents such as Claude, Cursor, and GitHub Copilot.

Central to the announcement is the Agentic Engineering Template, aimed at advanced adopters. According to Ming Wu, Head of Engineering for DevAI, the template works by setting up a Jira board where columns represent workflow states. When an issue moves from one column to another, agents are automatically assigned, creating a level of detailed and nuanced automation. This design allows developers to delegate routine tasks without interrupting their own work, while keeping all agent activity grounded in Jira's project history and knowledge base.

The motivation for these changes comes from a recognition that broad coding-agent adoption has not automatically delivered value. Research from Queen's University Kingston analyzing 61,000 repositories and 47,000 developers found that AI agent submissions are accepted less frequently than human-authored code and tend to be structurally simpler. Wu described this gap as a problem of coordination and context. Even as frontier AI models get smarter and faster, agents struggle without clear requirements, project context, proper handoffs, environment setup, and governance—what Atlassian calls the "work that surrounds work." The company believes the bottleneck is not agent capability but the lack of a cohesive solution to organize, prioritize, and track work across a mixed human-and-agent team.

Atlassian's strategy is to avoid positioning Jira as merely another tool and instead frame it as a solution spanning the entire software development lifecycle. Wu stated: "We need a solution rather than a tool... a solution across the entire software development lifecycle journey to actually address different pain points." By integrating agents from multiple vendors and automating assignment workflows, Atlassian aims to help companies realize return on investment from AI tool spending—a shift from simply boosting agent usage metrics to delivering measurable business value.

Context & Analysis

Atlassian's expansion of Jira reflects a broader recognition that the AI coding boom has hit a maturity plateau. While individual coding agents (such as GitHub Copilot and Claude) have seen rapid uptake, companies deploying them are discovering that raw code generation speed does not translate to project value. Research cited in the announcement—a study by Queen's University Kingston reviewing 61,000 repositories and 47,000 developers—found that AI agent submissions are accepted less frequently than human code and tend to be structurally simpler. This gap appears to stem not from agent capability alone, but from friction in the orchestration layer: agents lack clear requirements, project context, and integration with human workflows.

Atlassian's bet is that Jira, already the dominant project-management platform for software teams, can evolve into the control plane where developers and agents coordinate. By automating task assignment, providing context from project history, and embedding support for third-party agents (not just Atlassian's own Jira Coding Agent), the company aims to unlock the value trapped in isolated agent tools. Head of Engineering Ming Wu emphasized this strategy explicitly: "You want to bring the true value rather than boosting usage itself"—a clear signal that Atlassian is targeting return on investment, not just adoption metrics.

FAQ

What agents can be used with Jira?
Developers can assign work to the Jira Coding Agent or to third-party agents including Claude, Cursor, GitHub Copilot, and others, all while keeping the work tracked in Jira.
How does the Agentic Engineering Template work?
The template allows teams to set up a Jira board where columns represent workflow states, and agents are automatically assigned to issues as they move from one column to another, enabling more detailed and nuanced automation.
Why is Atlassian making these changes?
Atlassian sees that while coding-agent adoption is widespread, planning and coordination have become bottlenecks. The company wants Jira to address delays caused by unclear requirements, missing context, handoffs, documentation, and governance—what it calls the 'work that surrounds work.'

Get the latest Large Language Models news every morning

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytime

Discussion

No comments yet. Be the first to share your thoughts!

Log in to join the discussion

Related Articles

Stay ahead with AI news

Get curated AI news from 200+ sources delivered daily to your inbox. Free to use.

Get Started Free

Free · takes 30 seconds · unsubscribe anytime

1 minute a day. The AI essentials.

200+ sources · Email / LINE / Slack

Get it free →