Cannot Install Github for Jira

[Quincy Adler-Colvin]

Jira Cloud site: double-dev.atlassian.net
App: GitHub for Atlassian (com.github.integration.production)
Installation produces “We ran into a little trouble.”
The browser console reports useMarketplaceAppInstall: Failed to install the App and Atlassian’s feature-flag service returns HTTP 401 with “Invalid apiKey.”

The installer is an Organization admin and Jira Administration App admin. Please check the tenant’s Marketplace/app-installation provisioning and remove any incomplete installation record.

[James Gamble]

Hola Quincy,

The 401 “Invalid apiKey” from Atlassian’s feature-flag service is useful evidence, but I wouldn’t treat it by itself as proof that the tenant has a stale Marketplace installation record. There’s a more concrete Atlassian-documented condition worth checking first: Jira Cloud can fail Marketplace app installs with the same “We ran into a little trouble” message when the site doesn’t have an appropriate default product-access group configured. Atlassian documents that here.

I’d check admin.atlassian.com > select the site > Product access > Jira, then confirm that Jira has a normal default access group and that site-admins isn’t being used as the default group. If the default group is missing or incorrectly set, correct that and retry the GitHub for Atlassian installation.

That check is especially relevant because you’ve already confirmed the installer has organization-admin and Jira app-admin access, so this doesn’t appear to be a simple missing admin role.

If the default product-access configuration is already correct, I’d then test whether another free Marketplace app installs successfully. If a second app fails in the same way, that points much more strongly to a site-level Marketplace provisioning problem rather than anything specific to GitHub for Atlassian.

If other apps install normally and only GitHub for Atlassian fails, then I’d go to Apps > Manage your apps and check for any partial GitHub for Atlassian entry, as Viswanathan suggested. If there’s nothing removable there, I’d open an Atlassian Support case with the HAR file and console output, including the failed install request, the 401 response, the app key com.github.integration.production, and the site URL. Atlassian can inspect or clear the backend provisioning state that you can’t access from the UI.

I wouldn’t spend much time repeatedly clearing cookies or using multiple browsers unless Support asks me to. With a reproducible Marketplace installation failure and a backend 401, checking the documented site configuration and then escalating with a HAR is the cleaner path.

Thanks,

James

[Viswanathan Ramachandran]

Hi @Quincy Adler-Colvin 

The flag strongly points to an environment-level token, session, or stale provisioning state rather than a simple permission oversight. Try these

• Log out of Atlassian completely
• Try clearing the browser cache, cookies, restart and try again installing the app
• Or try incognito mode to install the app
• Check for Existing App Records
  
  1. Go to Jira Settings > Apps > Manage apps.
  2. Expand the filter dropdown and select All apps
  3. Search for GitHub for Jira 
  4. If you see, try select Uninstall.
• Try installing directly from the marketplace app - https://marketplace.atlassian.com/apps/1219592/github-for-atlassian
• If none works and issue still persists, please raise a support ticket with Atlassian https://support.atlassian.com