> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/helpdesks/jira-service-management/jira-service-management-setup.md).

# Set up Jira Service Management

Jira Service Management setup for your AI agent, screen by screen: create an Atlassian API token, then connect it in eesel, with a screenshot for each step.

Setting up Jira Service Management for your AI agent takes one API token from Atlassian and one secure form in eesel. An API token is a password-like key that lets eesel work in Jira. You create the token in your Atlassian account, then paste it into eesel with your Atlassian subdomain and email.

There is nothing to install from the Atlassian Marketplace.

## Before you begin

* You need a **Jira Cloud** site, at an address like `yourcompany.atlassian.net` or `yourcompany.jira.com`. Jira Server and Data Center are not supported.
* Pick the **Atlassian account** your agent will use. Your agent signs in as this account, so it sees and does only what this account can. Its replies and notes show this account's name.
* To turn on triggers, the account needs **rights to administer Jira automation** and must see at least one **Jira Service Management project**. eesel creates an Automation rule in Jira to hear about new issues and comments.
* Have your **subdomain** ready. It is the part before `.atlassian.net` in your Jira address. Use `yourcompany`, not `yourcompany.atlassian.net`. A site on `jira.com` is entered as `yourcompany.jira.com`.

## Walkthrough

{% stepper %}
{% step %}

### Open your Atlassian API tokens page

Sign in to Atlassian as the account your agent will use. Open [your API tokens page](https://id.atlassian.com/manage-profile/security/api-tokens). You can also get there from your Atlassian account: open **Security**, then **API tokens**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-ff938e6ebd06fea7e701a3c7be442827b71443b8%2Fconfluence-atlassian-api-tokens.png?alt=media" alt="The API Tokens page in Atlassian account settings under Security, with Create API token and Create API token with scopes buttons and a list of existing tokens"><figcaption><p>The API tokens page in your Atlassian account.</p></figcaption></figure>

Click **Create API token**. Do not use **Create API token with scopes**. eesel needs the plain token.
{% endstep %}

{% step %}

### Name the token and pick an expiry

Give the token a name your team will recognise, for example `eesel Jira`. Pick an expiry date, then click **Create**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-72c926231f3296bb7ed1b33bd4d9060c43d46851%2Fjira-atlassian-create-token.png?alt=media" alt="The Create an API token dialog in Atlassian, with the name eesel Jira filled in, an expiry date, and a Create button"><figcaption><p>The Create an API token dialog, with a name and an expiry date.</p></figcaption></figure>

Atlassian allows up to one year. A longer expiry means you reconnect less often. When the token expires, your agent stops working in Jira until you connect again with a new token.
{% endstep %}

{% step %}

### Copy the token

Atlassian shows the new token once. Click **Copy**, then click **Done**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-a05febe76a77100d19de9266a309367c7ad13b4a%2Fjira-atlassian-copy-token.png?alt=media" alt="The Copy your API token dialog in Atlassian, with the token masked, a Copy button and a Done button"><figcaption><p>The new token, masked, with the Copy button beside it.</p></figcaption></figure>

{% hint style="warning" %}
Copy the token before you click **Done**. Atlassian does not show it again. If you lose it, create a new one.
{% endhint %}
{% endstep %}

{% step %}

### Ask your agent to connect Jira Service Management

In the eesel dashboard, ask your agent in the chat to connect Jira Service Management. It asks for three things: your subdomain, your Atlassian email and the token.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-686a8895db88213d36dcbc82bbc68f72af7044aa%2Fjira-connect-chat.png?alt=media" alt="The dashboard chat where the user asks to connect Jira Service Management, and the agent lists the subdomain, the account email and an API token as the three things it needs"><figcaption><p>The agent lists the three details it needs.</p></figcaption></figure>

Prefer to click? Open **Integrations** in the left sidebar and pick **Jira**. It asks for the same three things.
{% endstep %}

{% step %}

### Give your subdomain and email

Reply in the chat with your subdomain and the email on the Atlassian account that made the token. A secure form appears in the chat with one field for the token.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-bedf36450f7b5cababb5340b45a30ea5f84139b9%2Fjira-secure-form.png?alt=media" alt="The dashboard chat after the user gives the subdomain and email, showing a secure form with a Jira API token field and a Save securely button"><figcaption><p>The secure form in the chat, with one field for the token.</p></figcaption></figure>
{% endstep %}

{% step %}

### Paste the token into the secure form

Paste the token into the form and click **Save securely**. The field masks the token as you paste it.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-7dae83245febf7f5156e5d0d6df3c72d2147dc3f%2Fjira-secure-form-filled.png?alt=media" alt="The same secure form with the Jira API token pasted in and shown as masked dots, ready to save"><figcaption><p>The form filled in, with the token masked.</p></figcaption></figure>

A person always pastes the token in. If an AI tool such as Claude Code runs the setup, it waits for you to do this step.
{% endstep %}

{% step %}

### Confirm the connection

Your agent picks the token up as soon as you save it. It confirms the connection and names the project it can see.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-8cb853b85dbb918c21e6397edfcdfe55651c75f4%2Fjira-connected-chat.png?alt=media" alt="The dashboard chat confirming Jira is connected, naming the project it can see and listing what it can now do with issues"><figcaption><p>The agent confirms the connection and names the project.</p></figcaption></figure>

**Check it worked.** Jira appears under **Integrations** in the left sidebar. Open it to see the connection, with your Atlassian site name and the actions your agent can take. From a terminal, `eesel status` lists the integration as connected.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-77d6fb9e74cea42b930a9d2924f3c6a427cd2c59%2Fjira-integration-page.png?alt=media" alt="The Jira integration page in eesel showing Connected with the Atlassian site name, a Jira source row with its document count and toggle, and the Read and Write action groups"><figcaption><p>The Jira integration page, marked Connected, with the Read and Write action groups.</p></figcaption></figure>

Connecting alone does not start your agent. To have it work on new issues, [create an automation](https://docs.eesel.ai/integrations/helpdesks/jira-service-management.md#create-your-first-automation).
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>The connection fails, or the form keeps reappearing</summary>

* Check the **subdomain** is only the part before `.atlassian.net`.
* Check the **email** is the one on the Atlassian account that made the token, not a team alias.
* Check you used **Create API token**, not **Create API token with scopes**.
* New tokens can take up to a minute to work. Wait a minute and connect again.

</details>

<details>

<summary>It worked, then every Jira action started failing</summary>

The token has probably expired, or someone revoked it. Create a new token and ask your agent to connect Jira Service Management again.

</details>

<details>

<summary>Turning on a trigger fails</summary>

The account behind the token needs rights to administer Jira automation, and must see at least one Jira Service Management project. Connect again with an account that has both, then turn the trigger on.

</details>

## FAQ

<details>

<summary>Is it safe to give eesel a Jira API token?</summary>

Yes. The token goes into a secure form, straight to eesel, never into the chat, and the form expires in 30 minutes. You choose which actions your agent may take, and which ones need your approval first.

</details>

<details>

<summary>Can I use the same token for Jira and Confluence?</summary>

Yes, if the account has both a Jira and a Confluence licence. It is the same kind of Atlassian API token. A separate token for each makes it easier to revoke one without breaking the other.

</details>

## Related pages

* [Jira Service Management](https://docs.eesel.ai/integrations/helpdesks/jira-service-management.md) for what your agent does in your service desk
* [Confluence](https://docs.eesel.ai/integrations/knowledge/confluence.md), which connects with the same kind of token
* [Actions and Approvals](https://docs.eesel.ai/instructions-and-memory/actions-and-approvals.md) for choosing what your agent may do
* [Set up from Claude Code or the terminal](https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent.md)


---

# 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.eesel.ai/integrations/helpdesks/jira-service-management/jira-service-management-setup.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.
