GitHub を Teamwork Graph に接続する

Use this guide to connect GitHub to Atlassian and make your GitHub data available across Jira, Rovo Search, and other Atlassian apps.

If you already have GitHub connected, you need to follow these steps to check that your app permissions are up to date to get the most out of your GitHub connector.

何がインデックス化されますか?

GitHub コネクタは、次のオブジェクトをインデックス化します。

• リポジトリ

• Pull requests and pull request comments

• Issues and issue comments

• Commits and branches

• Users, teams, and group memberships

• name

• URL

• created date

• last updated date

• creator

• collaborators

はじめる前に

• Marketplace app: You will need to have GitHub for Atlassian Marketplace app installed.

• Jira access: You need to be a site admin for the Jira site where GitHub for Atlassian is installed.

• GitHub access: You need a GitHub organization owner or equivalent who can review and accept app permissions.

• Compatibility: This connector is only compatible with GitHub Cloud (including Enterprise Cloud). GitHub Enterprise Server is not supported.

• Data access: When your teammates access GitHub data in Rovo at runtime, their own GitHub access is used. Repositories that haven't been restricted, and associated pull requests, issues, branches, and commits, will appear in search results for teammates who have access.

Step 1: Check your current permissions in GitHub

Before connecting (or if you already have GitHub connected), check whether your GitHub app installation has full permissions.

1. In GitHub, go to your organization settings and open the installed GitHub for Atlassian app.

2. In the Permissions column:

   • If it shows Full Access, you're all set. Skip to Step 3.

   • If it shows Limited, continue to Step 2.

Why this matters: Without full permissions, GitHub data is often limited to development activity linked to Jira issue keys. With full permissions, the connector can ingest data like users, teams, and memberships, and support newer experiences across Jira and other Atlassian apps.

Step 2: Accept the updated app permissions in GitHub

If your permissions are showing as Limited, a GitHub organization owner needs to accept the updated permissions:

1. Sign in to GitHub as an organization owner.

2. Open the GitHub for Atlassian app installation for the affected organization.

3. GitHub will show a permission update prompt. Review and accept updated permission scopes by selecting Accept new permissions.

Step 3: Connect GitHub in Atlassian Administration

Most organizations turn on the GitHub Teamwork Graph connector automatically while setting up the GitHub for Atlassian app, because it’s selected by default.

If you missed that step or are unsure, you can add the connector:

1. 移動 アトラシアンの管理。組織が複数ある場合は、対象の組織を選択します。

2. [アプリ] > [コネクタ] の順に選択します。

3. 複数のサイトがある場合は、接続するサイトを選択してから [コネクタを追加] を選択します。

4. Select GitHub, then Next. If GitHub is already showing as Connected, skip to Step 4.

5. GitHub 接続のニックネームを入力します。

6. データの使用に関する情報を確認して同意します。

7. [Connect] を選択します。

Step 4: Confirm organization and repository scope

After connecting (or after accepting updated permissions), confirm that the intended organizations and repositories are included in the connection.

1. As the site admin, go to Jira, select Apps, then Manage apps.

2. Open GitHub for Atlassian configuration.

   1. If your connection is set to All repositories, new repositories will be included automatically.

   2. If your connection is set to Only select repositories, review and add any repositories that should be in scope.

Step 5: Allow data to sync

Once your connection is set up and permissions are in place, GitHub content will start to appear in Search incrementally. Depending on the size of your GitHub environment, a full sync may take some time.

During the sync, avoid:

• Disconnecting and reconnecting the org

• Changing repository access scope

• Uninstalling/reinstalling the GitHub for Atlassian app

次のステップ

While syncing, your team members will see GitHub show up as a filter option in Search. If they haven't connected to GitHub from their Atlassian account, they may be asked to connect before they can see results. This is required to ensure teammates only see results they usually have access to.

トラブルシューティング

GitHub data looks incomplete or limited

• Check whether the GitHub organization owner has explicitly accepted the updated app permissions (see Step 2). If permissions are still showing as Limited, the connector will continue with reduced data coverage.

• Allow more time for sync to complete, especially in large environments.

• Confirm repository selection isn't unintentionally limited (see Step 4).

You can't find the permission update prompt in GitHub

• Confirm you're reviewing the correct GitHub app installation for the correct organization.

• If you use a customer-managed GitHub app, verify that the app's configured permissions match the recommended permissions for GitHub for Atlassian.

GitHub を Rovo から切断する

Because your GitHub data is integrated through the GitHub for Atlassian app, to disconnect your GitHub data from Rovo:

1. 移動 アトラシアンの管理。組織が複数ある場合は、対象の組織を選択します。

2. [アプリ] > [コネクタ] の順に選択します。

3. If you have more than one site, pick the site where your GitHub Teamwork Graph connector is installed.

4. Find the GitHub connector and select Manage from the Actions menu.

5. Turn off Show results in Rovo Search.