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

# Jira

Connect Arnica to your Jira Cloud workspace. Once connected, you can use Jira as the issue tracker for [Manual Issue Creation](/arnica-documentation/getting-started/ticket-management/creating-issues/manual-issue-creation.md) and [Automated Issue Creation](/arnica-documentation/getting-started/ticket-management/creating-issues/automated-issue-creation.md).

## Integration Steps

### Create a dedicated service account

Arnica authenticates via OAuth2 using a dedicated application user. Using a shared service account ensures the integration keeps working if the original user leaves.

{% hint style="warning" %}
The service account will appear as the reporter on every Jira issue Arnica creates. Name it clearly, e.g. `arnica-jira-service-account`.
{% endhint %}

1. Create a dedicated email address (e.g. `arnica-jira@yourcompany.com`). Use a shared inbox or alias so access is not tied to a specific person.
2. Go to [admin.atlassian.com](https://admin.atlassian.com) - your organization - **Directory - Users** and invite the email.
3. Complete the Atlassian account setup from the invitation email.
4. In Jira, add the service account to every relevant project with at minimum: **Browse Projects**, **Create Issues**, **Edit Issues**, **Transition Issues**.

{% hint style="info" %}
If connecting multiple workspaces, ensure the service account has equivalent access in each one.
{% endhint %}

Jira-side permissions are the primary requirement for issue creation. The Arnica user configuring the integration should have at least `Admin` permissions in Arnica.

### Integrate Jira with Arnica

1. Sign in to Jira as the **service account** - not your personal account.
2. In Arnica, navigate to **Admin - Integrations**, locate **Jira** and click **Connect**.

<figure><img src="/files/Rts35RaLupzE3k0WWddD" alt=""><figcaption><p>Locate Jira on the Integrations page and click Connect</p></figcaption></figure>

3. You will be redirected to Atlassian's OAuth authorization page. Review the requested permissions and click **Accept**.

<figure><img src="/files/P8d3RvY0yyNVmgvT3fKc" alt="" width="375"><figcaption><p>Authorize Arnica to connect to your Jira workspace</p></figcaption></figure>

4. If the integration was successful, the workspace will appear under the **Existing Integrations** section in Arnica.

<figure><img src="/files/cnc2bcxeMvR3Dx2dQJif" alt=""><figcaption><p>Jira connected and listed under Existing Integrations</p></figcaption></figure>

{% hint style="info" %}
Repeat for each additional Jira workspace.
{% endhint %}

## Remove a Jira Integration

1. Navigate to **Admin - Integrations**.
2. Find the Jira workspace you want to remove.
3. Click the **trash icon** next to the workspace.
4. Confirm the removal.

{% hint style="warning" %}
Disconnecting stops future issue creation but does not delete existing Jira issues created by Arnica.
{% endhint %}


---

# 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.arnica.io/arnica-documentation/getting-started/ticket-management/jira-integration.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.