Can GitHub Copilot for Jira be restricted to a specific repository, project and user group?

[Ait Benhida Fatimaezzahra]

Hi,
We are evaluating GitHub Copilot for Jira for our Jira Cloud instance.
Before installing it in production, I would like to understand the available restriction and administration options.
1. Can the integration be limited to a specific GitHub repository only?
2. Can the app be restricted to a single Jira project or board?
3. Can only a specific group of users be allowed to interact with GitHub Copilot from Jira?
4. Is there a way to run a pilot with one team before enabling it more broadly?
I would also like to understand the GitHub prerequisites:
5. How can I verify that GitHub Copilot is enabled and licensed for the users who will use the integration?
6. Does this verification require GitHub Organization Admin permissions?
7. As a Jira Administrator only, what information should I request from the GitHub administrators before installing the app?
Our goal is to start with one GitHub repository and one team only.
Thank you for your guidance.

[Viswanathan Ramachandran]

Hi @Ait Benhida Fatimaezzahra 

Running a controlled pilot is a best practice for rolling out AI integrations. You can indeed restrict the GitHub Copilot for Jira integration via the GitHub for Atlassian app and Jira Coding Agent across all three levels you mentioned.

1. Restricting the Integration Scope

• Repository Restriction: During the installation of the GitHub for Atlassian app on the GitHub side, you can choose "Only select repositories." This limits the integration’s visibility to only the specific repository you designate for the pilot.

• Jira Project/Board Restriction: The Copilot features in Jira are primarily managed through Jira Automation. You can scope these automation rules to a single project, ensuring the "Coding Agent" actions only trigger within your pilot team's workspace.

• User Group Restriction: You can manage application access within Jira by creating a specific Jira Group. By assigning this group to the app’s access settings, you ensure only authorised team members can interact with the Copilot features.

2. GitHub Prerequisites & Verification

• Licensing Verification: Verification is handled within GitHub. Your GitHub Administrator must confirm that the pilot users have been assigned a GitHub Copilot Business or Enterprise license. Jira relies on the user’s GitHub identity to validate their seat.

• Admin Permissions: Connecting the two platforms requires GitHub Organisation Owner permissions. As a Jira Admin, if you do not have these permissions, you can generate an Integration Request link from the Jira settings to send to your GitHub Admin for one-click approval.

• Information to Request from GitHub Admins:

  • The exact GitHub Organisation name.

  • Confirmation that GitHub Copilot is active for the organisation.

  • A list of GitHub usernames for the pilot team to ensure they match their Jira email addresses (crucial for identity syncing).

  • If your organisation uses a GitHub IP allowlist, ensure Atlassian’s IP ranges are added to avoid connectivity issues.

3. Pilot Strategy

To start with one team and one repository:

1. Install the GitHub app with access to one repository.

2. Create a Jira Group for the pilot team and restrict app access to that group.

3. Configure Jira Automation rules for the specific Jira Project only.

This multi-layered approach ensures that the rest of your Jira instance and GitHub organisation remain unaffected during your evaluation.

I hope this helps!