GitHub Copilot for Jira Is Generally Available
GitHub Copilot for Jira is now generally available, letting teams assign Jira issues to Copilot's cloud agent, follow progress in Jira, and continue work on the same draft pull request.
GitHub Copilot for Jira is now generally available after a public preview that started in March 2026. The integration lets teams assign Jira issues to GitHub Copilot's cloud agent, watch agent progress from the Jira issue, and add follow-up instructions in Jira chat after a draft pull request is opened. GitHub says the GA release also reduces setup friction and adds more control over agent sessions.
Key takeaways
- GitHub's June 25 changelog marks Copilot for Jira as generally available.
- Jira users can monitor the coding agent's progress without switching back to GitHub.
- Follow-up instructions can continue on the same draft pull request instead of spawning a new one.
- The Atlassian Marketplace listing confirms the app is a free commercial Jira Cloud app from GitHub.
- Teams still need to configure repository access and review pull requests before merging agent work.
Practical LinkLoot angle
This is useful for teams that already plan engineering work in Jira but review code in GitHub. The practical decision is whether Jira should become the front door for small implementation tasks, bug fixes, and backlog items that can be handed to a coding agent with clear repository boundaries.
| Option | Best use | Limitation | Source |
|---|---|---|---|
| GitHub Copilot for Jira | Assign Jira issues to Copilot cloud agent and get draft pull requests | Requires GitHub Copilot cloud agent access and repository configuration | GitHub, Atlassian |
| Manual Jira-to-GitHub handoff | Larger tasks that need human design before coding starts | Slower context transfer and more status chasing | Workflow comparison |
| GitHub-only Copilot sessions | Engineering teams that already manage task context inside GitHub | Less natural for teams where Jira is the system of record | GitHub Docs |
For LinkLoot readers building agent workflows, the key pattern is not "AI writes code from a ticket." It is controlled task routing: a Jira issue triggers an agent session, progress stays visible to non-GitHub stakeholders, and humans still review the generated pull request before it lands.
What to verify before you act
Check whether your GitHub plan and organization settings allow Copilot cloud agent use. Confirm which repositories the Jira app can access, because an agent workflow should not inherit broader permissions than the task needs. If your organization has data residency, procurement, or Atlassian app review requirements, compare the standard Marketplace app with the GitHub Enterprise Cloud data residency listing before rollout. Also test follow-up instructions on a low-risk issue first so the team understands how the agent keeps work on the same draft pull request.
Source check
GitHub's changelog confirms the GA milestone, progress streaming in Jira, follow-up instructions in Jira chat, reduced setup steps, and earlier preview enhancements such as model selection, Confluence context via MCP, custom agents, custom fields, space-level guidance, and review request notifications. The Atlassian Marketplace listing confirms the app is offered by GitHub, works with Jira Cloud, is listed as free, and is summarized as generally available. GitHub Docs confirm the supported setup path for integrating Copilot's cloud agent with Jira.
It is a GitHub app for Jira Cloud that lets teams assign Jira issues to GitHub Copilot's cloud agent and receive draft pull requests.
If you are mapping this into a broader agent stack, keep it beside LinkLoot's guide to AI workflow automation and document which tickets are eligible for agent assignment.