# Basic Configuration

**Settings** -> **Marketplace** **Apps** -> **GitHub integration for Jira**

<details>

<summary>Alternative configuration localizations</summary>

#### Company-managed spaces <a href="#company-managed-spaces" id="company-managed-spaces"></a>

[Manage your organization's Marketplace and third-party apps](https://support.atlassian.com/security-and-access-policies/docs/manage-your-users-third-party-apps/)

#### Team-managed spaces <a href="#team-managed-spaces" id="team-managed-spaces"></a>

[Manage Atlassian Marketplace apps in team-managed spaces](https://support.atlassian.com/jira-software-cloud/docs/manage-atlassian-marketplace-apps-in-team-managed-projects/)

</details>

{% stepper %}
{% step %}

#### **Connect your GitHub account**&#x20;

Use [GitHub OAuth](https://docs.gitconnector.com/master/github-oauth) or [Personal Access Token (PAT)](https://docs.gitconnector.com/master/using-personal-access-tokens)

{% hint style="info" %}
Each connected GitHub account is scoped to an individual Jira administrator and is **not shared** across users. **Jira users must connect their own accounts.**
{% endhint %}
{% endstep %}

{% step %}

#### Toggle the option: **inherit access permissions from GitHub**.

<figure><img src="https://2054987018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MSOOCh6RFWjUVTIii6J%2Fuploads%2FMErZPGmVrtu0oZdnp3nD%2Fimage.png?alt=media&#x26;token=fc2c2eff-7070-4525-a8af-c5457cf51d30" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**When enabled**

Per-project repository mapping is **not required**. Jira users can see the repositories they have access to in GitHub. You can still set [default-repositories](https://docs.gitconnector.com/master/default-repositories "mention")**,** if you do so, users will see the preselected repositories on the work item, but they can change them freely.
{% endhint %}

{% hint style="danger" %}
**When disabled**

Per-project repository mapping **is required**. Jira users can see the repositories they have access to in GitHub, but the list is additionally filtered by [default-repositories](https://docs.gitconnector.com/master/default-repositories "mention")**,** if you do not set that mapping, users will not see anything.

{% endhint %}
{% endstep %}
{% endstepper %}

<details>

<summary>Optional Steps</summary>

### How to Hide the Default Development Panel in Jira Work Items

*Disabling unused development features helps reduce noise.*

[How To Remove or Edit Access to Development Panel from Jira Work Items](https://support.atlassian.com/jira/kb/how-to-remove-or-edit-access-to-development-panel-from-jira-issues/)

### 1. Remove the Development Field from Layout

This removes the panel from the issue UI.

**Steps:**

1. Go to **Project Settings → Work Items → Layout**
2. Find the **“Development”** field
3. Remove it from the layout

<figure><img src="https://2054987018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MSOOCh6RFWjUVTIii6J%2Fuploads%2FpDfY2fucY9HnkqdrAkBZ%2Fimage.png?alt=media&#x26;token=97f3881c-2cf9-4191-b71b-febdc8dd206e" alt=""><figcaption></figcaption></figure>

### 2. Remove “View Development Tools” Permission

This ensures users cannot see development data even if the field exists.

**Steps:**

1. Go to **Jira Settings → Work Items → Permission Schemes**
2. Open your permission scheme&#x20;
3. Locate **“View Development Tools”**
4. Click **Remove**
5. Remove all groups, roles, or users

<figure><img src="https://2054987018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MSOOCh6RFWjUVTIii6J%2Fuploads%2FZWPeEfGMu2fMLmz1Yxvk%2Fimage.png?alt=media&#x26;token=c1618de0-0fb1-4644-b039-7b107e1fd329" alt=""><figcaption></figcaption></figure>

### 3. Disconnect Unused Git Integrations

Even with permissions removed, integrations may still attach some data.

</details>

​

{% content-ref url="../features/branch-templates" %}
[branch-templates](https://docs.gitconnector.com/master/features/branch-templates)
{% endcontent-ref %}

{% content-ref url="../features/project-configuration" %}
[project-configuration](https://docs.gitconnector.com/master/features/project-configuration)
{% endcontent-ref %}

{% content-ref url="../features/global-configuration" %}
[global-configuration](https://docs.gitconnector.com/master/features/global-configuration)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gitconnector.com/master/getting-started/basic-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.