What GitHub Announced

GitHub said on March 5, 2026 that GitHub Copilot coding agent for Jira is now in public preview. According to the changelog entry, teams can assign a Jira Cloud issue directly to the coding agent, which then reads the issue description and comments, works in a connected repository, and opens a draft pull request with the proposed changes. Progress is surfaced back into Jira so the ticket remains the coordination point.

The important shift here is not just that Copilot can write code, but that GitHub is moving the agent deeper into the system where engineering work is actually queued and tracked. In many teams, Jira is where work starts, while GitHub is where implementation happens. That handoff has traditionally required a human to translate issue context into branches, edits, and PRs. GitHub’s new flow is trying to compress that gap.

How the Workflow Works

GitHub says the agent can analyze the issue, make the requested code changes, open a draft PR, and even ask clarifying questions back in Jira when it needs more information. That makes the feature more than a simple integration hook. It turns Jira into an operating surface for coding agents, especially for well-scoped tasks such as bug fixes, maintenance updates, or documentation changes.

There are still enterprise constraints around the feature. GitHub says customers need Jira Cloud, Rovo enabled, GitHub Copilot coding agent, and a connected repository. The company also calls out data residency support, which matters for organizations that want workflow automation without relaxing existing governance and review boundaries.

Why It Matters

This release matters because it pushes coding agents beyond the editor and into the backlog itself. The broader trend is that assistant features are turning into workflow automation systems. GitHub’s Jira move is an example of that transition: the issue tracker is no longer just a planning tool, but increasingly a dispatch layer for software agents.

Source: GitHub

#jira

GitHub moves Copilot’s coding agent for Jira into public preview