> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/integrations/issue-tracking/integrate-with-jira-cloud.md).

# Integrate with Jira Cloud

You can connect Snyk API & Web with either Jira Cloud or your own Jira Server instance. This gives you two-way synchronization of your findings with Jira. Snyk sends a reported finding to Jira, and as soon as the finding is closed, Snyk triggers a retest. If the finding is fixed, the Jira issue remains closed. Otherwise, Snyk reopens it.

Regardless of your Jira setup, you must choose which targets to synchronize and how, either manually or automatically.

For information about integrating with Jira Server, visit [Integrate with Jira Server](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/integrations/issue-tracking/integrate-with-jira-server.md).

## Configure Jira synchronization settings

After connecting your Jira Cloud instance to Snyk, configure which targets to synchronize and how. The available options are the same for both Jira Cloud and Jira Server.

To set up the configuration, access the **Integrations** tab of your **Target Settings** and locate the **Jira Cloud** module, depending on the integration you configured.

### Project

Choose which Jira project to sync with.

### Issue Type

Choose the type of issue for the findings.

The available options depend on the project you chose. The same applies to the status and priority mapping that follows.

### Automatically sync all findings

If enabled, Snyk automatically synchronizes all findings, existing and future, with Jira. If disabled, you must choose individual findings to sync in each finding's details.

### Status mapping

Maps Snyk API & Web status to Jira status:

* **Not Fixed**: The initial state of the finding, right after Snyk reports it.
* **Invalid** (optional): The user changes the finding manually to report a false positive.
* **Accepted Risk** (optional): The user changes the finding manually to acknowledge it but accept its risk and not fix it.
* **Fixed**: Snyk confirms that the finding is fixed.

You can use each Jira status only once for each project.

### Priority mapping

Maps Snyk API & Web severity to Jira priority:

* **Critical**: A finding that represents a critical risk for the application and requires immediate remediation.
* **High**: A finding that represents a high risk for the application, whose exploitation can relatively easily cause damage to the application.
* **Medium**: A finding that alone is unlikely to cause damage to the application. However, if combined with another one, or in rare situations by itself, it can cause damage.
* **Low**: Alone, a low-risk finding does not compromise your application, except in extreme situations. The attacker normally requires another higher-risk finding to take advantage of this one.

After you finish, click **Save** so that you do not lose your changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/integrations/issue-tracking/integrate-with-jira-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.