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

# Install

Nullify integrates with Jira as an [Atlassian Forge](https://developer.atlassian.com/platform/forge/) app. The app is distributed privately via an install link provided by Nullify — it is not listed on the Atlassian Marketplace, and there is no app descriptor to upload or developer mode to enable.

## Install the Forge app

1. **Request an install link.** Your Nullify representative will provide an install link for the Nullify Forge app.
2. **Open the install link as a Jira site admin.** A Jira site administrator opens the link (or installs the app from the Atlassian admin console) and is taken to the Atlassian consent screen.
3. **Approve the requested scopes.** The consent screen lists the permissions the app needs. Approve them to continue:
   * Read the app system token
   * Read Jira work
   * Write Jira work
4. **Link the install to your tenant.** Once the app is installed, Nullify links the Forge installation to your tenant to complete setup.

That's it — there is no manual webhook to create. The Forge app declares its event triggers in its manifest, so inbound Jira issue and comment events (created, updated, and commented) flow to Nullify automatically. This is what lets Nullify reply to comments and keep tickets in sync.

## Issue Type

Each Jira issue has an issue type (for example: Bug, Task, or Story). By default, Nullify creates tickets using the **Task** issue type.

If you want Nullify to use a different issue type, set it in the Jira integration settings in the Nullify dashboard (see [Configuration](/connectors/jira/configuration.md)). The issue type you choose must exist in the target project.


---

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