GitHub Copilot for Jira: Custom Agents, Custom Fields, Branching Rules, and Space-Level Instructions
GitHub CopilotGitHub has shipped a new wave of enhancements to GitHub Copilot for Jira, building on the March 2026 public preview. Teams can now specify custom agents from their GitHub repository directly in a Jira ticket, give the agent access to Atlassian custom fields like acceptance criteria, enforce branch naming rules from within the ticket, and set space-level instructions that apply consistently across all agent invocations in an Atlassian space. A review notification is also added — when Copilot opens a draft PR requesting review, it posts a comment back to the originating Jira issue.
Sources & Mentions
3 external resources covering this update
GitHub Copilot for Jira Gets Deeper Customization and Workflow Integration
GitHub has released a substantial update to the GitHub Copilot for Jira integration, introducing four new customization capabilities that give teams significantly more control over how the Copilot cloud agent behaves when triggered from Jira tickets.
Custom Agents
Teams can now designate a custom agent from their GitHub repository directly within a Jira ticket. This allows organizations to leverage specialized agents — built with custom instruction files, specific tool configurations, or domain knowledge — rather than the default Copilot cloud agent. The custom agent specification is made inline in the Jira workflow, avoiding the need to reconfigure anything on the GitHub side for each individual issue.
Custom Field Support
The integration now reads Atlassian custom fields on Jira tickets and incorporates that context when the agent works on an issue. Acceptance criteria defined as a structured Jira field is a prime example: Copilot now pulls this directly into its understanding of what the implementation must achieve, moving beyond free-text descriptions toward machine-readable specifications.
Custom Branching Rules
When Copilot creates a pull request from a Jira issue, it now respects branch naming conventions specified within the Atlassian ticket. Teams enforcing naming schemas like feature/PROJ-123-description or jira/ticket-id can ensure the agent adheres to those patterns automatically, maintaining repository consistency without post-hoc branch renaming.
Space-Level Instructions
Administrators can now define space-level instructions in Atlassian — overarching directives that apply every time the Copilot cloud agent is triggered from any issue within a given space. These instructions can establish defaults for repository selection, branch naming, model choice, and preferred agent, reducing repetitive per-ticket configuration for teams with consistent workflows.
Review Notifications in Jira
When the Copilot cloud agent opens a draft pull request and marks it as ready for review, it now posts a comment back to the originating Jira issue. This closes a visibility gap: previously, a developer who assigned an issue to Copilot might not realize the agent had finished and was awaiting review unless they checked GitHub proactively. The notification keeps Jira as the source of truth for issue status even after work has crossed into GitHub.
Getting Started
The enhancements are available in the latest version of the GitHub Copilot for Jira app, which can be installed or updated from the Atlassian Marketplace.