# Git integrations for Jira

{% content-ref url="/pages/-MSOOFRoYh96xkgS5L0u" %}
[GitHub integration for Jira](/master)
{% endcontent-ref %}

{% content-ref url="/pages/-MkgTF8MxSScmLzCk4Xj" %}
[GitLab integration for Jira](/gitlab-integration)
{% endcontent-ref %}

{% content-ref url="/pages/-MkgUGPwA2kw2J\_J0hV\_" %}
[Azure DevOps integration for Jira](/azure-devops-integration-for-jira)
{% endcontent-ref %}


# GitHub integration for Jira

{% content-ref url="/pages/PKwMfkp3vtwa2NF8k1vB" %}
[Getting Started (Jira Admin)](/master/getting-started)
{% endcontent-ref %}

{% content-ref url="/pages/xRGMWsLrUr4ys6SToGSV" %}
[Getting Started (Jira User)](/master/getting-started-jira-user)
{% endcontent-ref %}

{% content-ref url="/pages/Sp38ksZQw7iZQTSZwRt3" %}
[Troubleshooting](/master/troubleshooting)
{% endcontent-ref %}

{% content-ref url="/pages/ZTxoHYfx1kF6C1CSuQs8" %}
[IP whitelisting](/ip-whitelisting)
{% endcontent-ref %}


# Getting Started (Jira Admin)

{% content-ref url="/pages/BwnILIVemnLZAHE5c6FN" %}
[Installation](/master/getting-started/installation)
{% endcontent-ref %}

{% content-ref url="/pages/EzerZivlneWf3vpl7sfi" %}
[Basic Configuration](/master/getting-started/basic-configuration)
{% endcontent-ref %}


# Installation

[Install the app from the Atlassian Marketplace.](https://marketplace.atlassian.com/apps/1224265/github-jira-integration?hosting=cloud\&tab=installation)


# 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>

<figure><img src="/files/vKKrEjhMZFgpvCfSAbNA" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

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

Use [GitHub OAuth](/master/github-oauth) or [Personal Access Token (PAT)](/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 %}

#### Set Up Repository Access

{% hint style="success" %}
**Option 1: Users inherit all repository access from their GitHub account**

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](/master/default-repositories)**,** if you do so, users will see the preselected repositories on the work item, but they can change them freely.
{% endhint %}

{% hint style="danger" %}
**Option 2: Users inherit GitHub repository access for selected repositories only**

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](/master/default-repositories)**,** 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="/files/i3m7Ma5lQctCLwWutBRW" 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="/files/ejhjuTgaWuezkI6EZcTA" alt=""><figcaption></figcaption></figure>

### 3. Disconnect Unused Git Integrations

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

</details>

​

{% content-ref url="/pages/KvKmZCkqPh4U5dONZdau" %}
[Branch Templates](/master/features/branch-templates)
{% endcontent-ref %}

{% content-ref url="/pages/RPHfDhO8pA6RHRmW49kM" %}
[Space Configuration (Project Configuration)](/master/features/project-configuration)
{% endcontent-ref %}

{% content-ref url="/pages/I7RlYOoiqbYk69CJS9rx" %}
[Global Configuration](/master/features/global-configuration)
{% endcontent-ref %}


# Getting Started (Jira User)

{% hint style="info" %}
[Integration panels](/master/ui-locations) should be visible on a [Jira work item](https://www.atlassian.com/software/jira/guides/issues/overview#what-are-parent-and-child-work%20items), where you can **connect** your Git account. If panels are not visible, ask your Jira administrator to enable the integration for your Jira Space (project).
{% endhint %}

## Connect with GitHub

{% content-ref url="/pages/GOZ2dUfVKogAAIn2KpDU" %}
[GitHub OAuth](/master/github-oauth)
{% endcontent-ref %}

{% content-ref url="/pages/qBj9GVJuILkvtKJc6Ag0" %}
[Personal Access Token (PAT)](/master/using-personal-access-tokens)
{% endcontent-ref %}

## UI Locations

{% content-ref url="/pages/RnpM05HTLrQbLsyTPQ38" %}
[UI Locations](/master/ui-locations)
{% endcontent-ref %}

## Features

{% content-ref url="/pages/8CUjUs3ymz06p9SfU8WT" %}
[Create Branch](/master/features/create-branch)
{% endcontent-ref %}

{% content-ref url="/pages/cnwkNy4jAfeJY9hyhBS1" %}
[Auto Branch Discovery](/master/features/auto-branch-discovery)
{% endcontent-ref %}

{% content-ref url="/pages/f1uMkEbFauqEV2FAPHYo" %}
[Manual Branch Linking](/master/features/manual-branch-linking)
{% endcontent-ref %}

{% content-ref url="/pages/7FkrcCvfqjhyZw7zU7fI" %}
[Delete Branch](/master/features/delete-branch)
{% endcontent-ref %}

{% content-ref url="/pages/dHDtUsVpgis3qqci1Asi" %}
[Create Pull Request](/master/features/create-pull-request)
{% endcontent-ref %}


# GitHub OAuth

{% stepper %}
{% step %}

### Click on the "GitHub OAuth" button

<div align="left"><figure><img src="/files/zaSuKiQUcWNXxirKxM4s" alt=""><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Sign in to GitHub in the opened window

{% endstep %}

{% step %}

### **Authorize access to your repositories and organizations**

<div align="left"><figure><img src="/files/rbeum91iIFOWdE8axlaa" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}


# Personal Access Token (PAT)

1. Create a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) in GitHub.

{% hint style="info" %}
For a classic token, selecting the `repo` scope is **required**.
{% endhint %}

<figure><img src="/files/TtQEwGkSkZPPD2SXWVlS" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You can also use a new fine-grained personal access token. In that case, select: **Permissions** → **Contents** → **Read and write access**.
{% endhint %}

2\. Go to your Jira instance.&#x20;

3\. Click on the "GitHub Enterprise PAT" button (available on Issue View, Configuration, and Project Configuration).

<figure><img src="/files/k4mEsrNoVTO9IJrej2hu" alt=""><figcaption></figcaption></figure>

4\. "Add a personal access token" will appear.

<figure><img src="/files/3HNftrkWtfOoTkMAeHJB" alt=""><figcaption></figcaption></figure>

5\. Provide your GitHub API URL and an access token.

6\. Click on the Save button.


# Default Repositories

<figure><img src="/files/jiK31DodqLq1hmJaERmp" alt=""><figcaption></figcaption></figure>


# UI Locations

{% hint style="info" %}
The plugin panels can be displayed on either **the left (1)** or **right side (2)** of a [Jira work item](https://www.atlassian.com/software/jira/guides/issues/overview#what-is-the-anatomy-of-an-work%20item), depending on the configuration set by the Jira administrator.
{% endhint %}

<figure><img src="/files/BpZXsQvpy2128zDUUBcz" alt=""><figcaption></figcaption></figure>


# Features


# Create Branch

{% hint style="info" %}
Create a branch with the [**work item key**](https://support.atlassian.com/jira-software-cloud/docs/what-is-a-work-item#Work-item-keys), and it will be automatically discoverable in the branches tab and other plugins.
{% endhint %}

{% hint style="info" %}
A **Jira administrator** can configure [Branch Templates](/master/features/branch-templates)
{% endhint %}

<figure><img src="/files/dP4hokp6JoEUjgSisQtP" alt=""><figcaption></figcaption></figure>


# Branch Templates

<figure><img src="/files/Iz5BXvotDTHe7aFhYKKq" alt=""><figcaption></figcaption></figure>

| Variable    | Description                                                                                                                   |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| prefix      | [Work item Type](https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types#Default-work-types) Prefix |
| issuekey    | [Work Item Key](https://support.atlassian.com/jira-software-cloud/docs/what-is-a-work-item#Work-item-keys)                    |
| summary     | Work Item Summary                                                                                                             |
| projectkey  | Project Key / Space Key                                                                                                       |
| displayname | Jira User Name                                                                                                                |
| gitusername | Git User Name                                                                                                                 |
| parentkey   | Work Item Parent                                                                                                              |

[Suggest more](https://gitconnector.atlassian.net/servicedesk/customer/portal/1)


# Auto Branch Discovery

{% hint style="info" %}
Branches containing [**work item key**](https://support.atlassian.com/jira-software-cloud/docs/what-is-a-work-item#Work-item-keys) are discoverable automatically.
{% endhint %}

<figure><img src="/files/VzPxj7ZL8TtYrS08VMEa" alt=""><figcaption></figcaption></figure>


# Manual Branch Linking

{% hint style="info" %}
You can link any branch manually to a Jira work item using the branch linking feature.\
**Pull Requests** for that branch are shown automatically in the **Pull Requests tab**.
{% endhint %}

<figure><img src="/files/ZmcNrf4xkcKMsqR9mfzm" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/28bUOfFIEooKjotnZl8K" alt=""><figcaption></figcaption></figure>


# Delete Branch

<figure><img src="/files/ug5CyYBx185NjziAMuFM" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ts58GIs7LIgv13Uo2559" alt=""><figcaption></figcaption></figure>


# Create Pull Request

<figure><img src="/files/FTJ3xOAm1KydWVFTWpRQ" alt=""><figcaption></figcaption></figure>


# Space Configuration (Project Configuration)

{% hint style="info" %}
From your space’s sidebar, select **Space settings**, then **Apps**.

Select an integration from the sidebar to view a **project configuration**.
{% endhint %}

<figure><img src="/files/9xqqdq79phYmWWBoytp3" alt=""><figcaption></figcaption></figure>


# Global Configuration

<figure><img src="/files/phcHsCMkMkOXzqztFXGr" alt=""><figcaption></figcaption></figure>


# Troubleshooting

{% stepper %}
{% step %}

### If your Git server is behind a firewall, make sure to whitelist the IP addresses used by GitConnector

{% content-ref url="/pages/ZTxoHYfx1kF6C1CSuQs8" %}
[IP whitelisting](/ip-whitelisting)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Organization repositories are not visible

1\. Go to your **GitHub** **Settings** page.

![](/files/yzLJ3uGyVLWJDVUewBfw)

2. Navigate to **Applications** and click on **GitConnector**.
3. Find your organization on the list and click **Grant**. If you do not see these buttons, then please switch to your organization account, navigate to **Third-party access**, and click on **Remove Restrictions**.
   {% endstep %}

{% step %}

### 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="/files/i3m7Ma5lQctCLwWutBRW" 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="/files/ejhjuTgaWuezkI6EZcTA" alt=""><figcaption></figcaption></figure>

### 3. Disconnect Unused Git Integrations

Even with permissions removed, integrations may still attach some data.
{% endstep %}
{% endstepper %}


# GitLab integration for Jira

Settings -> Marketplace Apps -> GitLab integration for Jira


# Getting Started (Jira Admin)

{% content-ref url="/pages/BEdGTCEXTyusTDAG6Wtf" %}
[Installation](/gitlab-integration/getting-started-jira-admin/installation)
{% endcontent-ref %}

{% content-ref url="/pages/iL9Y6CcMLdy0j4zLMneL" %}
[Basic Configuration](/gitlab-integration/getting-started-jira-admin/basic-configuration)
{% endcontent-ref %}


# Installation

[Install the app from the Atlassian Marketplace.](https://marketplace.atlassian.com/apps/1226096/gitlab-jira-integration?hosting=cloud\&tab=installation)


# Basic Configuration

**Settings** -> **Marketplace** **Apps** -> **GitLab 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>

<figure><img src="/files/WYhvBMEauenm2MDSAWOo" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

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

Use [GitLab OAuth](/gitlab-integration/gitlab-oauth) or [Personal Access Token (PAT)](/master/using-personal-access-tokens)

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

{% step %}

#### Set Up Repository Access

{% hint style="success" %}
**Option 1: Users inherit all repository access from their GitHub account**

Per-project repository mapping is **not required**. Jira users can see the repositories they have access to in GitLab. You can still set [Default Repositories](/gitlab-integration/default-repositories)**,** if you do so, users will see the preselected repositories on the work item, but they can change them freely.
{% endhint %}

{% hint style="danger" %}
**Option 2: Users inherit GitHub repository access for selected repositories only**

Per-project repository mapping **is required**. Jira users can see the repositories they have access to in GitLab, but the list is additionally filtered by [Default Repositories](/gitlab-integration/default-repositories)**,** 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="/files/i3m7Ma5lQctCLwWutBRW" 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="/files/ejhjuTgaWuezkI6EZcTA" alt=""><figcaption></figcaption></figure>

### 3. Disconnect Unused Git Integrations

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

</details>

​


# Getting Started (Jira User)

{% hint style="info" %}
[Integration panels](/gitlab-integration) should be visible on a [Jira work item](https://www.atlassian.com/software/jira/guides/issues/overview#what-are-parent-and-child-work%20items), where you can **connect** your Git account. If panels are not visible, ask your Jira administrator to enable the integration for your Jira Space (project).
{% endhint %}

## Connect with GitLab

{% content-ref url="/pages/Hfg3agh66fWNaJng7p7e" %}
[GitLab OAuth](/gitlab-integration/gitlab-oauth)
{% endcontent-ref %}

{% content-ref url="/pages/PltgY306ul59nveYim6H" %}
[Personal Access Token (PAT)](/gitlab-integration/using-personal-access-tokens)
{% endcontent-ref %}

## UI Locations

{% content-ref url="/pages/ZLQ8RGrRyWXzxax6O9YS" %}
[UI Locations](/gitlab-integration/ui-locations)
{% endcontent-ref %}


# GitLab OAuth

{% stepper %}
{% step %}

### Click on the "GitLab OAuth" button

<div align="left"><figure><img src="/files/ZBA6JLkBrQoTmCjlVskT" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Sign in to GitLab in the opened window

{% endstep %}

{% step %}

### Authorize access to your account on GitLab.com

<figure><img src="/files/eoyxWhAC8qrHOFcSM0TV" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


# Personal Access Token (PAT)

{% stepper %}
{% step %}

### Create a personal access token in GitLab

<https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html>

{% hint style="info" %}
API scope required
{% endhint %}

<figure><img src="/files/iFZYQC1KvIAEZiQaGeOW" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Go to your Jira instance

{% endstep %}

{% step %}

### &#x20;Click on the "GitLab PAT" button (available on Work Item)

<div align="left"><figure><img src="/files/fhqwgQ4dEdhkNrG5bJfM" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### The "Add a personal access token" window will be displayed

{% endstep %}

{% step %}

### &#x20;Provide your GitLab instance URL and the access token

<figure><img src="/files/o7nZaYnA7wuaiDBMSujQ" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### &#x20;Click on the Save button

{% endstep %}
{% endstepper %}


# Default Repositories

<figure><img src="/files/wKTWM1yXatTKcQtffquA" alt=""><figcaption></figcaption></figure>


# UI Locations

<figure><img src="/files/Wkw7hNRxfhp5K6qGthDy" alt=""><figcaption></figcaption></figure>


# Azure DevOps integration for Jira

## Installation

1. Log into your Jira instance.
2. Click the **Apps** dropdown and choose **Find new apps**. The *Find new apps* screen loads.
3. Search for **Azure DevOps integration for Jira** and click on the app tile. The *App Details* screen loads.
4. Click **Try it free** to start installing your app.
5. You're all set! Click **Close** in the *Installed and ready to go* dialog.

## Configuration

1. Go to the configuration page (**Apps** -> **Azure DevOps integration for Jira**).
2. Connect your account using [PAT (Personal Access Token)](/azure-devops-integration-for-jira/using-personal-access-tokens).
3. Select repositories related to your projects.

![](/files/-MkhBNupbnacpxGffT0v)


# Using personal access tokens

1. Create a [personal access token in Azure](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops\&tabs=Windows), the minimum required scope is Code (Read & Write).&#x20;

<figure><img src="/files/v0n2hCNLwHU4PdXWcNaq" alt=""><figcaption></figcaption></figure>

2\. Go to your Jira instance.&#x20;

3\. Click on the "Azure Personal Access Token (PAT)" button (available on Issue View, Configuration, and Project Configuration).

![](/files/HKJoMQrqnCSg3df4TpE3)

4\. "Add a personal access token" will appear.

![](/files/DPckdB74G1bwli0zCI6B)

5\. Provide your Azure API URL and an access token.

6\. Click on the Save button.


# IP whitelisting

You may need to add the following IP addresses to your allow list if your server has restrictive firewall settings:

```
159.89.243.216
161.35.249.14
3.135.68.213
```

Protocol HTTPS, Port 443

{% hint style="info" %}
**Atlassian IPs and domains must also be allowed to ensure that Atlassian Cloud apps and services work as expected**

<https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/>
{% endhint %}


# Security Statement

February 2, 2026

* We use encrypted connections (TLS) whenever it is possible&#x20;
* We enforce 2FA (two-factor authentication) for core systems
* We use source code dependency scanning tools
* We host data provided by customers on DigitalOcean, Inc.&#x20;
* We create daily data backups on DigitalOcean, Inc. and Amazon Web Services
* Daily data backups are available for a minimum of ten subsequent days
* Our services are hosted on DigitalOcean, Inc.

## Security Bug Fix Policy

The following table describes when we resolve security bugs in our products:

| **Severity**                            | Resolution time                                  |
| --------------------------------------- | ------------------------------------------------ |
| <p></p><p><strong>Low</strong></p>      | <p></p><p> within 175 days of being reported</p> |
| <p></p><p><strong>Medium</strong></p>   | <p></p><p>within 84 days of being reported</p>   |
| <p></p><p><strong>High</strong></p>     | <p></p><p>within 42 days of being reported</p>   |
| <p></p><p><strong>Critical</strong></p> | <p></p><p>within 10 days of being reported</p>   |