Integrating Copilot cloud agent with Jira - GitHub Docs
Skip to main content Skip to content Collapse sidebar Expand sidebar Integrating Copilot cloud agent with Jira You can use the GitHub integration in Jira to provide context and open pull requests, all from within your Jira workspace. Who can use this feature? Available for all paid Copilot plans . In this article Note GitHub Copilot uses AI. Check for mistakes. See Application card: GitHub Copilot Agents . The GitHub Copilot integration in Jira allows you to invoke Copilot cloud agent without leaving your Jira workspace.
From within Jira you can initiate cloud agent sessions and open pull requests, using the context of the work item's title, description, labels, comments, and any Atlassian custom fields such as acceptance criteria. Prerequisites You must have a GitHub account with access to Copilot through a paid Copilot plan. You must have a Jira Cloud account, Jira must be an AI-enabled app , and Rovo must be activated for your organization.
See Activate AI for apps in the Atlassian documentation. Installation and authentication must be completed for both Jira and GitHub. Installation To install the GitHub Copilot for Jira app and authorize it for your GitHub organization or enterprise account, you need: Administrator permission for your Jira site. Owner or GitHub App manager permissions for your GitHub organization. This integration relies on an Atlassian Forge application and a GitHub application.
Both are required for the integration. Once successfully installed, authorized users of the Jira workspace with write access to a GitHub repository will be able to trigger the agent from Jira. Installing the GitHub Copilot for Jira app for GitHub.com Navigate to the GitHub Copilot for Jira installation page on the Atlassian Marketplace. Click Get it now . Select the Atlassian site you want to install the GitHub application in.
Click Review to check the installation details, and then click Get it now . Once GitHub Copilot for Jira is installed in your Jira site, you need to authorize the app to access your GitHub organization and repositories. Click Configure in the confirmation message in Jira after installation. If you are not automatically redirected, go to the GitHub Copilot for Jira installation page on the GitHub Marketplace. Click Install .
If you are not already logged in to GitHub, click the highlighted Log in to GitHub and follow the prompts to log in to your GitHub account and authorize the application. If your organization or enterprise uses single sign-on (SSO), you may need to start an active SAML session for your organization and perform an additional authorization step. Click Install app to give the app permission to access information on your GitHub account.
Choose the organization and repositories the app has access to. Your GitHub organizations are enabled by default for your Jira workspace. Optionally, in the Install GitHub Copilot for Jira page, deselect the organization and repositories you don't want the application to have access to . Click Install . When installation is complete, you will see a list of connected organizations on the GitHub Copilot for Jira app configuration page in Jira.
Installing the GitHub Copilot for Jira app for GHE.com Navigate to the GitHub Copilot for Jira (GHEC with Data Residency) installation page on the Atlassian Marketplace. To the right of the app name, click , and enter your SUBDOMAIN.ghe.com in the text box. Replace SUBDOMAIN with your enterprise's subdomain of GHE.com. Click Save configuration . Click Get it now . Select the Atlassian site you want to install the GitHub application in.
Click Review to check the installation details, and then click Get it now . Once GitHub Copilot for Jira is installed in your Jira site, you need to authorize the app to access your GitHub organization and repositories. Click Configure in the confirmation message in Jira after installation. If you are not automatically redirected, find the GitHub Copilot for Jira app in the list of apps available to your enterprise at SUBDOMAIN.ghe.com/apps/external-app/github-copilot-for-jira .
Click Install . If you are not already logged in to GitHub, click the highlighted Log in to GitHub and follow the prompts to log in to your GitHub account and authorize the application. If your organization or enterprise uses SSO, you may need to start an active SAML session for your organization and perform an additional authorization step. Click Install app to give the app permission to access information on your GitHub account.
Choose the organization and repositories the app has access to. Your GitHub organizations are enabled by default for your Jira workspace. Optionally, in the Install GitHub Copilot for Jira page, deselect the organization and repositories you don't want the application to have access to . Click Install . When installation is complete, you will see a list of connected organizations on the GitHub Copilot for Jira app configuration page in Jira.
Using the GitHub Copilot app in Jira The Copilot app must be enabled for a GitHub organization you are a member of, before you can start using it. The first time you use Copilot cloud agent in Jira, you will need to connect it to your GitHub account. Only users with write access to a repository can trigger Copilot cloud agent to work in that repository. You can trigger Copilot cloud agent in several ways: Assign GitHub Copilot to a work item using the Assignee field.
Mention @GitHub Copilot in a comment on a work item. Use a Jira automation. In your Jira automation rules, select the Use GitHub Copilot action and configure your flow to use a custom trigger based on Jira events, such as when a work item is created or transitioned, or a label is applied. For more information, see Work with AI agents in Jira in the Atlassian documentation. Note When you assign Copilot to a Jira work item, the context the agent captures from Jira will be added to the pull request and visible to everyone if the repository is public.
Example: Triggering Copilot cloud agent from a Jira work item In Jira, open or create a work item that contains clear requirements you want to delegate to Copilot cloud agent. To specify a repository you want Copilot to work in, mention it in the work item description or in a comment. Assign GitHub Copilot to the work item, or mention @GitHub Copilot in a comment. For example: @GitHub Copilot create a new API endpoint for user authentication in octo-org/octorepo If you have not previously connected the GitHub application in Jira to your GitHub account, follow the prompts to authorize the application for both GitHub and Atlassian.
Once Copilot cloud agent has started working on the pull request, a comment will appear in the chat panel in Jira. The user who initiated the agent session can view progress there. You can follow up with further instructions for Copilot: Use the Continue in Chat button under the Agents heading to chat directly with Copilot to have updates made to the current pull request. Mention @GitHub Copilot in a comment on the work item to have updates made in a new pull request.
Tip If you have not received confirmation of triggering Copilot cloud agent after 1 minute, refresh the Jira work item page. Viewing agent activity in Jira While cloud agent works its activity streams live into the chat panel in Jira, so you can follow what the agent is doing without leaving your work item. The activity stream includes a link to the associated agent session on GitHub. Directing Copilot from Jira post-session When Copilot cloud agent has completed a session, for example when a pull request is ready for review, you can direct Copilot to continue the work: In the chat panel in Jira, select the link to the associated agent session on GitHub.
This opens the agents panel on GitHub, where you can review the session and send follow-up instructions to update the existing pull request. Add a follow-up @GitHub Copilot mention or comment on the Jira work item. This starts a
The rest of this page is on the live site.