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

# Jira Cloud

To authorize Jira, navigate to your **Workspace Settings**, open the **User Integrations** page, find the **Jira** integration, and click **Connect**. You'll then be prompted to enter your credentials.

## Required Jira Permissions

Paradime authenticates to Jira with an **Atlassian API token** (Jira Cloud) or a **Personal Access Token** (Jira Data Center). These tokens carry no scopes of their own — they act as the user who created them, so the token owner's Jira account needs the project permissions for the actions you want DinoAI to perform:

| DinoAI action                                 | Jira project permission |
| --------------------------------------------- | ----------------------- |
| Fetch, list, and search issues                | Browse Projects         |
| Create issues                                 | Create Issues           |
| Update summary, description, labels, priority | Edit Issues             |
| Change issue status                           | Transition Issues       |
| Change assignee                               | Assign Issues           |
| Add comments                                  | Add Comments            |

{% hint style="success" %}
**Tip:** Connect Jira with a dedicated service account whose project permissions cover exactly the actions above. Since API tokens are unscoped, the account's permissions are the real boundary of what DinoAI can do in Jira.
{% endhint %}

{% hint style="info" %}
Read-only usage (fetching and searching issues) only requires **Browse Projects**. If your organization uses Atlassian's newer scoped API tokens, the equivalent scopes are `read:jira-work` for reading and `write:jira-work` for creating, updating, and commenting.
{% endhint %}

For **Jira Data Center** users, see [Connecting Jira Data Center to Paradime ](/app-help/documentation/integrations/code-ide/jira-data-center.md)for setup instructions specific to your environment.

Once connected, DinoAI will be able to access Jira on your behalf using the [Confluence Tool](/app-help/documentation/dino-ai/tools-and-features/confluence-tool.md).

### Jira Cloud

{% hint style="info" %}
You will need an Atlassian API key to connect Jira Cloud. See the table below for instructions on where to find each required field.
{% endhint %}

| Field             | Description                                              | Where to find it                                                                                     |
| ----------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Jira Domain**   | The subdomain of your Jira Cloud account                 | Your Jira URL, e.g. `https://your-org.atlassian.net`                                                 |
| **Email Address** | The email address associated with your Atlassian account | Your Atlassian account profile                                                                       |
| **API Key**       | A personal API key to authenticate requests              | Go to [id.atlassian.com](https://id.atlassian.com) → **Security** → **Create and manage API tokens** |

Once all fields are filled in, click **Connect** to complete the connection.


---

# 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.paradime.io/app-help/integrations/jira/jira-cloud.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.