> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/jira.md).

# Jira

Read issues, search with JQL, and browse projects on Jira Cloud.

## What It Enables

| Tool                  | Capability | Description                                                       |
| --------------------- | ---------- | ----------------------------------------------------------------- |
| `search_issues`       | `read`     | Search issues using JQL (e.g. `project = ENG AND status != Done`) |
| `get_issue`           | `read`     | Get one issue with its full description as plain text             |
| `list_issue_comments` | `read`     | List an issue's comments, newest last                             |
| `list_projects`       | `read`     | List Jira projects with key, name, and lead                       |

All tools are read-only. Descriptions and comments are converted from Atlassian Document Format (ADF) to plain prose.

## Setup

**Required:** Atlassian account email + API token, and the Jira Cloud site URL (e.g. `https://acme.atlassian.net`).

**Where to find it:** [id.atlassian.com → Security → API tokens](https://id.atlassian.com/manage-profile/security/api-tokens)

1. In the Notara dashboard, go to **Tools**.
2. Click the **Jira** tile.
3. Go to Atlassian's API token page and click **Create API token**.
4. Copy the token.
5. Paste the token, your account email, and your site URL into the connector fields.
6. Click **Verify & Save**.

Your API token is encrypted at rest with AES-256-GCM.

## Example Prompts

> "What are all the open P1 bugs in the ENG project updated in the last week?"

> "Summarize the description and latest comments on ENG-423."

> "List all projects owned by the backend team."


---

# 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://notara.gitbook.io/notara-docs/connectors/jira.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.