> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/jira.md).

# Jira

The Jira connector for Elimity Insights fetches users, groups and roles from Jira so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Setting up a dedicated user in Jira

As usual, we recommend creating a dedicated user in Jira for this connector. Make sure this user has sufficient rights in your organization, refer to [the official documentation](https://support.atlassian.com/user-management/docs/give-users-admin-permissions/#Make-someone-an-organization-admin.1) for detailed instructions. Note down the new user's username and your organization's Atlassian URL (e.g. `https://example.atlassian.net`) for later use.

## 2. Generating an API token for the dedicated user

Having created a new user in Jira, we now need to generate an API token for authentication. Refer to [the official documentation](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token) for detailed instructions. Note down the generated token for later use.

## 3. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Jira source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>Username</td><td>Username you noted down in step 1.</td></tr><tr><td>Token</td><td>API token you generated in step 2.</td></tr><tr><td>Base URL</td><td>Your organization's Atlassian URL, which you noted down in step 1.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/jira.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.