---
updatedAt: 2026-08-18T11:46:09.000Z
agentTools:
  projectIndex: https://docs.socket.dev/llms.txt
---

# Jira Integration

Connect your Jira Cloud instance to Socket to create and manage tickets from alerts, with manual creation and automated ticketing rules.

<Callout icon="📘" theme="info">
  The Jira integration is available on Business and Enterprise plans.
</Callout>

Connect your Jira Cloud instance to Socket to create and manage Jira tickets directly from Socket alerts. Create tickets manually from individual alerts, or set up automated ticketing rules that create, update, and resolve Jira issues based on alert events in your organization.

The integration is powered by the **Socket for Jira** Atlassian Forge app, which is installed in your Jira Cloud instance and connected to your Socket organization.

### Key capabilities

* **Manual ticket creation** — Create a Jira ticket from alerts in the Socket dashboard.
* **Automated ticketing rules** — Define rules that automatically create Jira tickets when specific alert events occur, with configurable conditions, issue types, priorities, labels, assignee and additional fields.
* **Two-way sync** — When Jira issues are updated, resolved, or deleted, Socket is notified and can update the alert accordingly.
* **Multi-organization support** — A single Jira site can optionally be connected to multiple Socket organizations.

## Prerequisites

* Confirm your Socket account is on a **Business** or **Enterprise** plan.
* Have a Jira Cloud instance ready (Jira Server and Data Center are not supported).
* Hold an **Owner** or **Admin** role in your Socket organization (required to connect the integration).

## Connect Jira to Socket

### Step 1: Install the Socket for Jira app

Go to **Dashboard → Settings** for your organization and select "**Jira**" in the menu (under “**Integrations**”).

1. Click the "**Connect**" button.
2. Click the installation link. This will open a new window in Atlassian.
3. Click "**Get app**", select the site and click "**Install**".

<Callout icon="📘" theme="info">
  You must have Jira admin permissions to complete the installation.

  If you cannot install apps directly, request installation from your Jira administrator.
</Callout>

<Image src="https://files.readme.io/b679e9d4a85ecfa4020fbf081cde22f345a47a58f111014dcc711bc9cf0a3a48-image.png" align="center" width="600px" />

### Step 2: Open the app configuration page

Once installed, navigate to the app's configuration page:

1. Go to **Atlassian Administration** → **Apps** → **Sites** → select your Jira site.
2. In the list of **Connected apps**, find **Socket for Jira**.
3. Click the **three-dot menu** (⋯) on the right side and select **Configure**.

<Image src="https://files.readme.io/eaec2bc5c86c70198adc23d97926a106dcf533a0f3907ad431840beffb15045a-image.png" align="center" width="600px" />

### Step 3: Connect the app to Socket

On the configuration page:

1. Click the **Connect to Socket** button. This opens the Socket dashboard in a new window.
2. If you are not already logged in, sign in to your Socket account.
3. Confirm which Socket organization to connect to your Jira site.
4. Click **Connect** to complete the setup.

Once connected, the configuration page in Jira shows a success message confirming the connection.

<Image src="https://files.readme.io/236e038129c4ecd7d3527d81dfe1c212bd6ac9758859fbe9cf592eda71b98793-image.png" align="center" width="600px" />

<Callout icon="📘" theme="info">
  Only Socket administrators (Owner or Admin role) can complete the connection step. If you are not an administrator, copy the connection link from the Jira configuration page and share it with your Socket administrator.
</Callout>

### Step 4: Verify the connection

In the Socket dashboard, go to **Settings** → **Integrations** → **Jira**. You should see your Jira site listed with a **Connected** status badge, along with details about who connected it and when.

<Image src="https://files.readme.io/faaf9e6f618d78e723db81df82639e542258f66cf96176d180b4df8df4f1c865-image.png" align="center" width="600px" />

## Disconnect Jira

To disconnect a Jira site from your Socket organization:

1. Go to **Settings** → **Integrations** → **Jira** in the Socket dashboard.
2. Find the Jira site you want to disconnect.
3. Click **Disconnect**.

<Image src="https://files.readme.io/58e7130b259e9b237cd8a8462184a1651bb2c931a0e92b805712cf4de9a8e874-image.png" align="center" width="600px" />

This removes the link between the Jira site and your Socket organization. The Socket for Jira app remains installed in Jira and can be reconnected later.

## Multi-organization support

By default, a Jira site can be connected to a single Socket organization. To connect the same Jira site to multiple Socket organizations:

1. Open the **Socket for Jira** configuration page in Jira (see Step 2 above).
2. Enable the **Allow this app installation to be used with multiple organizations** toggle.
3. Use the **Connect to Socket** button again to link additional Socket organizations.

<Image src="https://files.readme.io/bb7f69832c7d7044836aab5de46dbecb3c550f263339536b365d2268fb6cb046-image.png" align="center" width="600px" />

## Create Jira tickets from alerts

Once the integration is connected, you can create Jira tickets directly from alerts in the Socket dashboard.

1. Open an alert in the Socket dashboard.
2. Click the **Create Ticket** button.
3. Select the Jira site, project, issue type, and fill in any additional fields.
4. Submit to create the ticket.

The created ticket is linked to the alert. A link to the Jira ticket appears on the alert, allowing you to navigate directly to it.

<Image src="https://files.readme.io/c5f9d4e820eec51d1c0af86dd966dd1918e56a2841fd96f38cfaf6a406f6e7f1-image.png" align="center" width="600px" />

## Automated ticketing rules

Automated ticketing rules let you define conditions under which Jira tickets are automatically created, updated, or resolved. Configure these rules from **Settings** → **Integrations** → **Ticketing** in the Socket dashboard.

<Callout icon="📘" theme="info">
  Ticketing is available on Business and Enterprise plans.
</Callout>

### Create a ticketing rule

Click **Create Configuration** to start the 5-step wizard:

#### 1. Select events

Choose which events should trigger the rule.

<Image src="https://files.readme.io/382bdbce49f0bd1f7e8c3a9d9839adc94bbd4a9aad5ed65c99280a3dc8df604f-image.png" align="center" width="600px" />

#### 2. Select conditions

Optionally define conditions to filter which alerts match this rule. This lets you target specific alert types, priority levels, repositories or other attributes.

<Image src="https://files.readme.io/f3f8504825b4b83ffcd73766af2812fa2fd86c5ad1c593d2293ae5384f7ccc47-image.png" align="center" width="600px" />

#### 3. Select project

Choose the Jira connection and project where tickets should be created:

* **Integration** — Select which connected Jira site to use.
* **Project** — Seach and select the Jira project where tickets will be created.

<Image src="https://files.readme.io/84f9ad5a91063ea6ecd41af4b9631a045c7b369f0de4910686ec3b26b22a6f3e-image.png" align="center" width="600px" />

#### 4. Configure issue

Define how the Jira issue should be created:

* **Issue type** — Select the Jira issue type (e.g., Bug, Task, Story).
* **Priority** — Set a specific priority, or use **Auto** to have Socket map the alert priority to a Jira priority automatically.
* **Labels** — Optionally add labels to created issues.
* **Assignee** — Optionally assign the issue to a specific team member.
* **Additional fields** — Configure any other fields supported by your Jira project.

<Image src="https://files.readme.io/f3a2c0863a8a64b42df5b85fca3eba1c71ccbe26ad6ed5a97ee52eeeba9a4f27-image.png" align="center" width="600px" />

#### 5. Configure actions

Define what happens when alert state changes:

* **Create issue** — Automatically create a new Jira issue when the rule conditions are met.
* **Update issue** — Update the linked Jira issue when the alert is updated. Additionally you can transition the Jira issue to a specific status when the alert is cleared in Socket.
* **Ignore alert** — Optionally triage-ignore the Socket alert when the linked Jira ticket is closed.

<Image src="https://files.readme.io/499e241780a25a7119993813877dc257ad74516dadb18a5d159c76b3d017c281-image.png" align="center" width="600px" />

After reviewing the summary, click **Create** to activate the rule.

<Image src="https://files.readme.io/60f69e3e4afe552c3e0b10d5e2e4864a3573cb92e141cca3b08d220a2e79c3cc-image.png" align="center" width="600px" />

## Permissions

### Socket roles

| Role        | Capabilities                                   |
| ----------- | ---------------------------------------------- |
| Owner       | Connect, disconnect, configure ticketing rules |
| Admin       | Connect, disconnect, configure ticketing rules |
| Member      | View connections, create tickets from alerts   |
| Contributor | View connections                               |

### Jira app permissions

The Socket for Jira app requests the following Jira permissions:

* **Read Jira work** — Required to read issue data such as projects, issue types, priorities, statuses, and labels.
* **Write Jira work** — Required to create and update Jira issues on behalf of the integration.

The app does not access or modify any other Jira data.

## Troubleshooting

<Accordion title="The 'Connect to Socket' button is not visible" icon="circle-question">
  The connection URL is only available after the Socket for Jira app has been installed and has completed its initial setup. If the button is missing, try refreshing the configuration page.
</Accordion>

<Accordion title="Connection token is invalid or expired" icon="circle-question">
  Connection tokens expire after 7 days. If you see a warning that the token is invalid or expired, go back to the Jira configuration page and click **Connect to Socket** again to generate a fresh token.
</Accordion>

<Accordion title="I cannot complete the connection" icon="circle-question">
  Only users with **Owner** or **Admin** roles in the Socket organization can complete the connection. If you have a different role, copy the connection link from the Jira configuration page and share it with an administrator.
</Accordion>

<Accordion title="Tickets are not being created automatically" icon="circle-question">
  Verify the following:

  1. The ticketing rule is set to **Active** status.
  2. The Jira site is still connected (check **Settings** → **Integrations** → **Jira**).
  3. The alert event matches the rule's event and condition filters.
  4. The Jira project and issue type are still valid in your Jira instance.
</Accordion>

<Accordion title="I have another problem" icon="circle-question">
  If you encounter problems or have questions not explained here, please do not hesitate to [contact support](https://docs.socket.dev/docs/contact-support).
</Accordion>

## Next steps

* [Webhooks](https://docs.socket.dev/docs/webhooks) — Set up webhooks to receive real-time notifications for alert events.
* [Customizable Security Policies](https://docs.socket.dev/docs/enabled-issues) — Configure which alert types trigger warnings and blocks across your organization.
* [Organization Alerts](https://docs.socket.dev/docs/organization-alerts) — Review and manage alerts across all repositories in your organization.