-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Integration - Github - Marketplace
-
None
-
1
Problem Summary
Currently, when multiple Jira Cloud sites connect to a single shared GitHub Cloud organization using the GitHub for Atlassian integration, there is no mechanism to isolate or partition repository access per Jira site.
Because the GitHub App is installed at the GitHub organization level, repository permissions applied in GitHub (Only select repositories) apply globally to the entire app installation. As a result:
- All repositories authorized in the GitHub organization are exposed across all connected Jira Cloud sites.
- Any work item in any connected site or space can link to any repository authorized in the organization if a matching work item key is referenced.
- Independent repository access control and security boundaries between different Jira Cloud sites sharing an enterprise GitHub organization cannot be enforced.
Suggested Solution
1. Per-Site Repository Mapping: Allow Jira administrators to define which repositories from a connected GitHub organization should sync with a specific Jira Cloud site.
2. Space-Level Repository Scoping: Provide the ability within Jira Cloud space settings to restrict repository selection and linking to explicitly mapped repositories.
3. Multi-Tenant GitHub App Handshake: Enable the integration service to filter webhook ingestion and development panel queries so that events from Repository X are only processed and visible within the designated Jira Cloud site.
Current Workarounds
- Moving repositories into entirely separate GitHub organizations
- Restricting the "View Development Tools" permission per space
- relates to
-
JRACLOUD-89951 Connecting multiple Jira sites to a single Github Org causes issues with multiple projects syncing smart commits
-
- Long Term Backlog
-