> 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/configure-jira-synchronization-settings.md). # Configure Jira synchronization settings How to configure Jira synchronization settings for Snyk API & Web {% hint style="info" %} **Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface. {% endhint %} ## Configure Jira synchronization settings 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 by integrating Snyk with your existing bug tracker or task manager. Regardless of your Jira setup, you must choose which targets to synchronize and how. The available options are the same for both Jira Cloud and Jira Server. For information about connecting Snyk with your Jira Server instance, visit [Integrate with Jira Server](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/integrations/issue-tracking/integrate-with-jira-server.md). ### Access the Jira integration settings To set up the configuration, access the **Integrations** tab of your **Target Settings** and locate the **Jira Server** or **Jira Cloud** module, depending on the integration you want to configure. If the integration is available to set up, you see the following screen: ### Configure synchronization options #### 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/integrations/issue-tracking/configure-jira-synchronization-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.