> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/connectors/jira/configuration.md). # Configuration Nullify creates a new issue in Jira for each finding above the configured threshold. The Jira connector is configured from the Nullify dashboard under **Configure -> Ticketing** (and the per-integration Jira settings) — there is no `.nullify.yml` file. In the Jira integration settings you set the **Project Key** and the **Issue Type**: * **Project Key** is the key of the target Jira project. This is the same key that appears in the URL when you are in the project. * **Issue Type** is the type of issue Nullify creates. The default is **Task**. You can find the available issue types in your Jira project settings under Issues -> Types (the URL is of the form `https://your-team.atlassian.net/plugins/servlet/project-config/YOUR-PROJECT-KEY/issuetypes`). You may prefer to create a dedicated issue type for Nullify's findings if you want to track tickets opened by Nullify separately. Create it in Jira first, then select it in the dashboard. ## Optional Configuration ### Severity and Priority Threshold By default, Nullify creates tickets using the same severity and priority thresholds reported in the dashboard. You can also set thresholds specific to ticket creation under **Configure -> Ticketing**, per finding type. For example, you might want the issues dashboard to include all findings of severity MEDIUM or higher, but only create a Jira ticket for findings that are URGENT. Nullify's priority taxonomy is `URGENT`, `IMPORTANT`, `MEDIUM`, and `LOW`, so you might surface everything at IMPORTANT or higher on the dashboard while only ticketing URGENT findings. ### On Fix Nullify closes the ticket in Jira when the underlying finding is fixed. By default, the ticket transitions to the last (right-most) column on your board. If you want a different target status when a finding is fixed, set the fix transition in the Jira integration settings to the status you want. The match is case-insensitive, and the target status must already exist in the project workflow. ### Disable You can disable automatic Jira ticket creation from the dashboard. A typical use case is when you have the Jira connector configured globally but want to turn off automatic ticket creation for a specific repository — for example, an internal tool or script that is not used in production. You can also disable *automatic* ticket creation while keeping the project key and issue type configured, so that you can still *manually* create tickets from the dashboard when needed. --- # 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.nullify.ai/connectors/jira/configuration.md?ask=&goal= ``` `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.