# Priorities

Nullify will automatically assign priorities to tickets based on the severity of the ticket. Nullify will use the default Jira priorities of `highest`, `high`, `medium` and `low`.

If your JIRA project uses a different priority schema, you can specify that in your `.nullify.yml` file. The `priorities` field is optional, and if no priorities are specified, Nullify will use the default Jira priorities mentioned above.

The `priorities` field is a mapping from the vulnerability severities to Jira priorities. The severities are `critical`, `high`, `medium` and `low`. The priorities are the Jira priorities you want to use for the tickets.

```yaml
integrations:
  jira:
    project_key: EXAMPLE
    [other options]
    priorities:
      critical: Critical
      high: Important
      medium: Routine
      low: Low
```

It is possible to specify or omit priorities in either the global configuration file or the repository level configuration file. If you specify priorities in the global configuration file, they will be used for all repositories. If you specify priorities in the repository level configuration file, they will override the global priorities.

It is possible to specify priorities in the global configuration file but not in the repository configuration file. This can be useful if you use the same priority schema across your organization, but want to change only the project key for each repository without having to respecify the priorities.


---

# Agent Instructions: 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:

```
GET https://docs.nullify.ai/connectors/jira/priorities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.