---
type: "post"
id: "atlassian-announces-factory-droid-integration-in-jira-via-7a2287"
slug: "atlassian-announces-factory-droid-integration-in-jira-via-7a2287"
title: "Atlassian announces Factory Droid integration in Jira via Rovo Chat and the Agents picker"
description: "Atlassian has made Factory’s Droid coding agent callable from a Jira work item through Rovo Chat."
retrieval_nugget: "Atlassian has made Factory’s Droid coding agent callable from a Jira work item through Rovo Chat."
published_at: "2026-10-28"
updated_at: "2026-10-28"
record_date: "2026-10-28"
date_kind: "published_at"
topics: ["mcp"]
entities: ["Atlassian","Jira","Factory","Droid","Rovo Chat","Atlassian MCP","Forge Remote Agent","A2A"]
related_patterns: ["agent-protocols-become-interoperability-layer","verification-bandwidth-is-the-scarce-resource","agent-ready-software-exposes-capabilities"]
novelty_label: "same_event"
what_changed: "Same event as Factory appears as a Rovo agent in Jira's Agents picker."
prior_refs: ["memory:9e119c21-da55-8988-a9d6-41bca1d11cd9","memory:cee81282-dd25-84cf-a5c8-6180ad640e13","memory:dc316b7b-3989-8660-ad81-2302be5eb976"]
source_url: "https://www.atlassian.com/blog/jira/factory-in-jira"
source_urls: ["https://www.atlassian.com/blog/jira/factory-in-jira"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:atlassian-announces-factory-droid-integration-in-jira-via-7a2287"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/atlassian-announces-factory-droid-integration-in-jira-via-7a2287/","markdown":"https://newruntime.com/posts/atlassian-announces-factory-droid-integration-in-jira-via-7a2287.md","json":"https://newruntime.com/posts/atlassian-announces-factory-droid-integration-in-jira-via-7a2287.json"}
---

# Atlassian announces Factory Droid integration in Jira via Rovo Chat and the Agents picker

## Retrieval answer

Atlassian has made Factory’s Droid coding agent callable from a Jira work item through Rovo Chat.

## Summary

Atlassian has made Factory’s Droid coding agent callable from a Jira work item through Rovo Chat. The agent can take the issue, retrieve Jira and Confluence context, run in a configured environment, stream status into Jira, and write its result back. For teams building with AI, the change moves agent handoff closer to the place where work is assigned and tracked.

## What happened

On October 27, 2026, Atlassian announced an integration that lets Factory’s Droid coding agent be invoked directly from a Jira work item through Rovo Chat. Atlassian describes the intended workflow as handing a Jira issue to an agent rather than manually moving issue context into a separate coding surface. Droid takes the task, performs engineering work in the environment selected for it, and returns results to the Jira item. Jira therefore remains the point where planning, assignment, execution status, and the returned output meet.

The first time an engineer uses Droid, they configure the agent by selecting a compute environment, model settings, and service accounts. Those settings can be retained as defaults for later tasks. Once invoked, Droid picks up the Jira work item, pulls relevant Jira and Confluence material through Atlassian MCP, runs the coding task in the configured environment, streams progress into Jira chat, and writes results back to the work item. Atlassian says the integration began with a request from an enterprise customer in a regulated industry that was building a software factory in a controlled environment; Factory built the Forge Remote Agent for Jira in response.

The integration is implemented as a Forge Remote Agent using the A2A protocol. Factory is described as model-independent and able to deploy across Factory-managed compute, customer infrastructure, and fully air-gapped environments. That matters for organizations that need to choose where an agent executes and which models it uses, rather than treating the Jira connection as a requirement to move code or context into one hosted runtime. The announcement does not identify supported models or detail the operational differences between those deployment options.

Availability is aimed at Jira Cloud customers with Rovo enabled. A Factory organization links to one Jira site, and Droid is configured on first use. Atlassian frames the product change as a way to remove the manual work of re-supplying ticket context, operating an agent elsewhere, and reconciling the eventual output with the originating issue. The public announcement does not state a price, a usage limit, or a general availability date beyond the publication date.

## What the archive adds

This is a new integration event on a known Factory handoff story. Factory had already made [Delegations generally available](https://newruntime.com/posts/factory-made-delegations-generally-available-for-handing-droid-30660f/) across connected team applications, including Jira, and had separately documented [Jira delegation prerequisites](https://newruntime.com/posts/factory-now-supports-jira-delegations-485380/). The Atlassian announcement adds the product architecture and in-Jira execution path: Rovo Chat, Atlassian MCP context retrieval, a Forge Remote Agent, and A2A.

## Trend signal

This supports [Agent protocols become the interoperability layer](https://newruntime.com/patterns/agent-protocols-become-interoperability-layer/). The useful interface here is not a model-specific prompt window: Jira exposes the work item and its context, while a Forge Remote Agent uses A2A to connect Factory’s execution system to Atlassian’s surface. It also puts pressure on the archive assumption that [verification bandwidth is the scarce resource](https://newruntime.com/patterns/verification-bandwidth-is-the-scarce-resource/): easier delegation can increase the number of outputs awaiting review.

## Why now

The stated trigger was an enterprise customer in a regulated industry seeking a controlled software-factory setup. Atlassian’s framing suggests that the problem is no longer merely access to a coding model; it is preserving the issue tracker as the system of record while allowing execution to occur in a chosen, potentially customer-controlled environment.

## Connections to other events

The earlier Factory Delegations release moved the request surface into applications such as Slack, Linear, Jira, and Teams. This announcement narrows into Jira and describes the execution plumbing behind that handoff. It is therefore more than a new mention syntax: it specifies how task context, agent progress, and returned results can remain attached to a Jira work item.

## Why it matters

Teams often experience agent adoption as a coordination problem rather than a generation problem. A developer can already use a coding agent, but a ticket still needs context assembled, an execution environment chosen, credentials governed, progress communicated, and output reconciled with the original task. This integration places those steps around the Jira issue and lets an organization establish defaults for compute, models, and service accounts.

That can reduce context copying and make agent work more observable to a team that already operates from Jira. It does not make a Jira ticket a sufficient specification, nor does a written result establish that code is correct, secure, merged, or released. The likely operational benefit is strongest where teams can pair explicit task scopes with an existing review path and a controlled execution environment.

## What happens next

- **More organizations will treat Jira issues as agent-dispatch objects rather than only planning records.** (6 months, 65%). Watch for: additional agent integrations that return progress and artifacts to the issue.
- **Review queues will become a clearer limiting factor for teams expanding these handoffs.** (6 months, 70%). Watch for: approval, test-evidence, and merge-control features around agent-produced work.

## Limits and uncertainty

The announcement is a vendor description of its own integration, not an independent evaluation of task quality, security, or productivity impact. It does not provide benchmarks, customer deployment numbers, pricing, model lists, supported repositories, permissions detail, or a breakdown of what runs in each compute option. It also does not establish whether the returned Jira result includes a pull request, code diff, test evidence, or only a summary. The term “autonomous” describes the handoff and execution flow, but the source gives no basis for assuming that every assigned issue can be completed without human clarification, review, or release approval.

## Skill to build now

Choose one low-risk Jira issue type and turn it into an explicit agent contract this week: define the repository and allowed services, the expected artifact, required tests, the reviewer, and the condition for closing the ticket. Then compare the agent’s Jira updates with the original issue and review evidence. This makes the new handoff surface useful without confusing visible progress with accepted engineering work.

## Reader takeaway

Factory’s Jira integration makes the issue tracker a control surface for dispatching Droid, selecting governed execution settings, following work in progress, and receiving a result. The significant change is the workflow boundary, not a claim that coding review disappears: teams that benefit will be those that can turn Jira tasks into sufficiently bounded, verifiable agent assignments.

## Open question

Will the integration expose enough structured evidence—diffs, test results, approvals, and deployment state—for Jira to support reliable acceptance rather than simply record an agent’s completion message?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)