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

Automatic ticket creation is off by default — enable it per finding type under Configure -> Ticketing, where you also set the threshold at which a ticket is created.

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. The priorities you can set a ticket threshold to are URGENT and IMPORTANT — so you might surface everything at IMPORTANT or higher on the dashboard while only ticketing URGENT findings.

Nullify only auto-creates tickets for findings at IMPORTANT priority or above, regardless of the threshold you set. To capture a lower-priority finding, create the ticket manually from the dashboard.

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.

Scoping automatic creation

Because automatic ticket creation is enabled per finding type, you can keep it on for the finding types that matter and off for the rest. A typical use case is enabling it globally but turning it off for a specific repository — for example, an internal tool or script that is not used in production.

You can also leave automatic creation off while keeping the project key and issue type configured, so you can still manually create tickets from the dashboard when needed.