> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/integrations/aqua4jira-plugin-cover-jira-issue-with-aqua-test-cases/installing-plugin-for-jira-data-center.md).

# Installing plugin for Jira Data Center

If you are using **Data Center**, navigate to Jira Data Center plugin store by clicking on the **Settings** icon and then select  **Manage apps.**

<figure><img src="/files/MPm5ZneyfleujEWKDyH8" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/v52uReNvHhluKkNahCFG" alt=""><figcaption></figcaption></figure>

In the Jira plugins store, simply type "aqua" into the search bar to find the plugin.

<figure><img src="/files/AMnYvKlX20CZIWzdwA7B" alt=""><figcaption></figcaption></figure>

Once it's there the **Install** button.&#x20;

&#x20;

<figure><img src="/files/fCrjB68089Hvs6T53j6a" alt=""><figcaption></figcaption></figure>

Then navigate to **Manage apps**

<figure><img src="/files/dng0XViSVVTyQ62kCHLb" alt=""><figcaption></figcaption></figure>

At the **Manage apps** page, select **aqua Configuration** from the sidebar.

<figure><img src="/files/jBWeVsfYfIoETR3ZoV6U" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}

### **aqua pre-requisites**

To connect the plugin, you need to create a **technical user** in aqua and assign them the **Jira plugin license**.

This license is included with every paid aqua subscription by default, at no extra cost.

Creating a technical user works the same way as adding any other user in aqua.\
For step-by-step instructions, check out our guide: [*How to add a new user*.](/documentation/user-administration/adding-and-editing-user-profile.md#adding-user)

Once user is created, you need to assign all projects from which you'd like to link test cases and test scerios (suites). Since technical user doesn't modify any items, a role with read-only permissions will suffice.
{% endhint %}

At the configuration page, please provide:

* Your server URL
* You API username
* Your API user password

<figure><img src="/files/qU91FbLq2KONaCxZUaEL" alt=""><figcaption></figcaption></figure>

Next, choose whether you want to enable test cases, test scenarios, or both.

You can also restrict access to specific Jira projects if needed.

Once you've set your preferences, click **Save** to apply the configuration.

The plugin is ready to be used.

**Alternative option to upload plugin**

You can upload your plugin manually. At the plugin configuration page select **Upload app**&#x20;

<figure><img src="/files/NlO4frRwQRH4CJ3XdZtT" alt=""><figcaption></figcaption></figure>

Then select the Jar file or by specifying a network location by entering a URL.

<figure><img src="/files/MHHP8BK1SlUoZtlYggts" alt=""><figcaption></figcaption></figure>

Upload the JAR file using the file chooser or by specifying a network location by entering a URL.

Click **Upload**. A confirmation message appears when the plugin is successfully installed.&#x20;

Then configure it as described above.


---

# 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.aqua-cloud.io/documentation/integrations/aqua4jira-plugin-cover-jira-issue-with-aqua-test-cases/installing-plugin-for-jira-data-center.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.
