> 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/priorities.md).

# Priorities

Nullify automatically assigns a priority to each Jira ticket based on the finding's priority. By default it maps to the standard Jira priorities of `highest`, `high`, `medium`, and `low`.

If your Jira project uses a different priority scheme, you can configure the mapping in the Jira integration settings in the Nullify dashboard. The mapping is optional — if you do not configure one, Nullify uses the default Jira priorities above.

The mapping goes from Nullify's priority taxonomy to your Jira priorities. Nullify's priorities are `URGENT`, `IMPORTANT`, `MEDIUM`, and `LOW` (note these are Nullify's priority labels, not Jira severity terms like CRITICAL/HIGH). For each Nullify priority you choose the Jira priority you want the ticket to use, for example:

| Nullify priority | Jira priority |
| ---------------- | ------------- |
| URGENT           | Critical      |
| IMPORTANT        | Important     |
| MEDIUM           | Routine       |
| LOW              | Low           |

The priority mapping you set in the dashboard applies to all tickets Nullify creates in that Jira project, so you can keep a single consistent priority scheme across your organization.


---

# 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/priorities.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.