> ## Documentation Index
> Fetch the complete documentation index at: https://sentrydocs.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Jira
> Create and link Jira tickets from Sentry issues, and keep status and assignees in sync.
The Jira integration connects your Sentry organization to one or more Jira Cloud instances. You can create Jira tickets directly from Sentry issues, link to existing tickets, and synchronize status and assignee changes between the two systems.
## What you can do
* Create a Jira ticket from any Sentry issue with a single click
* Link a Sentry issue to an existing Jira ticket
* Sync assignees between Sentry and Jira automatically
* Resolve Sentry issues when the linked Jira ticket is marked done
* Post Sentry comments to linked Jira tickets
* Automatically create Jira tickets via alert rules when new issues appear
## Install the Jira integration
The Jira integration is installed through the Atlassian Marketplace, not directly from Sentry.
Go to the [Sentry for Jira listing](https://marketplace.atlassian.com/apps/1219432/sentry-for-jira) on the Atlassian Marketplace and click **Get it now**.
You need Jira admin permissions to install Marketplace apps. If you do not have admin access, ask your Jira administrator to complete this step.
Choose the Jira Cloud site where you want to install the Sentry add-on, then complete the Marketplace installation flow.
After installation, open the Sentry add-on settings inside Jira. Enter your Sentry organization slug and follow the prompts to authorize the connection.
In Sentry, go to **Settings > Integrations** and confirm that Jira appears as an installed integration.
## Create a Jira ticket from a Sentry issue
Navigate to the Sentry issue you want to track.
In the issue sidebar, click **Link Jira Issue**, then select **Create new issue**.
Select the Jira project and issue type, then fill in the title, description, and any other required fields. Sentry pre-fills the title and a link back to the Sentry issue.
Click **Save**. Sentry creates the Jira ticket and links it to the issue. The ticket key appears in the Sentry issue sidebar with a direct link to Jira.
## Link to an existing Jira ticket
If a Jira ticket already exists for an issue:
1. In the Sentry issue sidebar, click **Link Jira Issue**, then select **Link existing issue**.
2. Search for the Jira ticket by key or title.
3. Select the ticket from the results and click **Save**.
## Configure sync settings
You can configure bidirectional syncing from **Settings > Integrations > Jira > Configure**:
| Setting | What it does |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Sync Jira Status to Sentry** | Resolves or unresolves the Sentry issue when the linked Jira ticket status changes to or from a "done" category |
| **Sync Jira Assignment to Sentry** | Assigns the Sentry issue when the Jira ticket is assigned |
| **Sync Sentry Assignment to Jira** | Assigns the Jira ticket when the Sentry issue is assigned |
| **Sync Sentry Status to Jira** | Changes the Jira ticket status when the Sentry issue is resolved or unresolved |
| **Sync Sentry Comments to Jira** | Posts comments from Sentry issues to the linked Jira ticket |
Assignee syncing matches users by email address. The user must have the same email in both Sentry and Jira for the sync to work.
### Map Jira statuses
When you enable **Sync Sentry Status to Jira**, you configure a per-project mapping between Sentry's resolved/unresolved states and specific Jira statuses. This lets you map "resolved" in Sentry to the appropriate done status in each Jira project.
You also choose what happens in Sentry when the Jira ticket is resolved:
* **Resolve** — marks the Sentry issue as resolved
* **Resolve in Current Release** — resolves in the currently deployed release
* **Resolve in Next Release** — resolves in the next release
### Hide Jira fields
If your Jira projects have custom fields you do not want to see when creating tickets from Sentry, add the field IDs to the **Ignored Fields** setting under **Settings > Integrations > Jira > Configure**. Enter comma-separated field IDs (for example: `components, security, customfield_10006`).
## Automatically create Jira tickets with alert rules
You can configure alert rules to automatically create a Jira ticket whenever a new Sentry issue matches certain conditions.
1. Go to **Settings > \[Project] > Alerts** and create or edit an alert rule.
2. Under **Actions**, select **Create a Jira issue**.
3. Choose the Jira project, issue type, and any other required fields.
Each alert rule action creates a new Jira ticket every time it fires. Use the condition "issue is new" to avoid creating duplicate tickets for recurring errors.
## Troubleshooting
**The Jira integration does not appear in Settings > Integrations.**
Make sure the Sentry add-on was installed through the Atlassian Marketplace and that the connection to your Sentry organization was completed inside Jira's add-on settings.
**Assignee sync is not working.**
Verify that the user's email address is identical in both Sentry and Jira. The sync matches accounts by lowercase email.
**Status changes in Jira are not updating Sentry issues.**
Check that **Sync Jira Status to Sentry** is enabled and that the Jira status you are transitioning to is in the "done" status category in Jira's workflow configuration.
**I cannot see certain Jira fields when creating a ticket.**
Fields may be hidden because they are in the **Ignored Fields** list. Check **Settings > Integrations > Jira > Configure** and remove any fields you need.