Factory and Atlassian have unlocked something big for our shared customers: Factory’s Droid coding agent can now be invoked directly from a Jira work item. Droid picks up the task, runs the engineering work in the selected environment, and writes results back to Jira. It’s the first time teams can hand a Jira issue to a coding agent, use whatever AI model fits their needs, and keep everything running inside their own secure environment.

🎯 The problem

Engineering work starts in Jira, but giving a coding agent the full context and workflow from an issue still takes manual work. Developers re-feed context by hand, run the agent on a separate surface, and the results never make it back to the ticket.

🚀 What’s new

Factory’s Droid coding agent can now be invoked directly from a Jira work item through Rovo Chat. Droid picks up the task, runs the engineering work in the selected environment, and writes results back to Jira — turning the board into the control point for both planning and execution. The integration started with a request from an enterprise customer in a regulated industry that’s building a software factory in a highly controlled environment. That customer brought Factory and Atlassian together, and Factory built the Forge Remote Agent for Jira.

💡 Why it matters

Using AI in development is not the same as orchestrating work with it. Most developers already use AI, but teams still lose time rebuilding context, managing prompts, and reconciling work across tools. Droid in Jira gives teams a direct path from assigned work to autonomous execution while preserving Jira as the system of record. And because Factory is model-independent and deploys across Factory-managed compute, customer infrastructure, and fully air-gapped environments, enterprises keep control over where agents run and which models they use.

⚙️ How it works

From a Jira issue, an engineer invokes Droid in Rovo Chat. On the first run, they configure the Droid — selecting a compute environment, model settings, and service accounts — and those settings can become the default for future tasks. From there, Droid:

  1. Picks up the Jira work item.
  2. Pulls relevant Jira and Confluence context through Atlassian MCP.
  3. Runs the coding task in the configured environment.
  4. Streams progress into the Jira chat.
  5. Writes results back to the work item.

The integration runs as a Forge Remote Agent using the A2A protocol.

✅ Availability

The Forge Remote Agent is designed for Jira Cloud customers with Rovo enabled. Each Factory organization links to one Jira site, and Droid is configured on first use.

🔗 Get started