Authenticate GitHub to run mitigation steps in Incident Command Center
Incident Command Center (ICC) is currently available through an early access program (EAP). Features, interfaces, and availability may change as development continues.
Incident Command Center is available to Jira Service Management customers on Premium and Enterprise plans.
Learn how to connect and authorize your GitHub account to investigate incidents and create mitigation plans in Incident Command Center in Jira Service Management.
はじめる前に
Confirm you have access to the incident view in Jira Service Management.
Confirm you have a GitHub account with write permission to the target repository.
If your GitHub organization enforces OAuth app access restrictions, a GitHub organization owner must approve the Atlassian OAuth app.
Connect your GitHub account
GitHub for Jira Service Management uses OAuth to authorize actions on repositories your GitHub account can access. When you trigger an action and are prompted to authenticate:
In the Mitigation tab, select Authenticate now and sign in to the GitHub account you want to use.
Select the GitHub organization that contains the target repository.
Approve or request app access:
For organization owners: Select Grant to approve access for your organization's members.
For organization members: Select Request if the app is not yet approved. GitHub will send an email request to the organization owner. Wait for the owner to approve access before retrying.
Once access is approved, return to the incident in Jira Service Management and select Rerun.
Organization owners can approve pending requests directly from the notification email or in GitHub by going to Settings > Organizations > [Your organization] > Third-party access > OAuth app policy and approving Atlassian Cloud.
Switch to a different GitHub account
The GitHub account you select upon initial authorization is linked to your Atlassian account. If you previously connected multiple GitHub accounts, revoke access for all of them so Atlassian doesn’t fall back to an unintended account.
To remove access for previously connected GitHub accounts:
Go to your Atlassian personal account settings and open Credentials.
Revoke access for the Atlassian app associated with all previously connected GitHub accounts.
Return to the incident and retry the action.
When prompted to re-authorize, select Authenticate now, sign in with the intended GitHub account, and complete the authorization steps.
Troubleshoot connection issues
If you encounter issues connecting your GitHub account or running actions, check the following:
Repository permissions: Verify that you are signed in to the correct GitHub account and that it has write access to the repository.
Pending organization approval: If your organization restricts third-party OAuth access, ask a GitHub organization owner to approve the Atlassian Cloud app request.
Wrong account linked: If Atlassian continues linking to a different GitHub account, revoke all previous Atlassian OAuth authorizations in your Atlassian account settings, then re-authenticate.
この内容はお役に立ちましたか?