> 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/product-updates-for-on-premise-customers/product-updates/2025/25.18.0-on-premise.md).

# 25.18.0 - On premise

Explore the 25.18.0 On Premise product update - find detailed release notes, enhancements, and fixes specific to this version for on-premise deployments.

We’re bringing you **powerful new updates** designed to make your work **smoother, more secure, and more efficient**! Let’s dive in:

### 🔄 **PAT for Jira Sync – A more secure way to sync projects**

Good news for teams using **Jira Data Center**! You can now set up **sync between Jira and aqua projects using a Personal Access Token (PAT)** instead of basic authentication. This ensures a **more secure** and **reliable integration** between the two platforms.

👉 [**Learn how to set up PAT for Jira sync here.**](https://docs.aqua-cloud.io/documentation/integrations/jira-sync-synchronize-items-between-aqua-and-jira-projects/sync-of-the-projects-between-aqua-and-jira)

{% hint style="info" %}
**Switching from basic authentication to PAT?** You’ll need to **recreate your syncs** to apply the change.
{% endhint %}

### 📊 **License usage statistics & Excel export**

Keeping track of **who’s using your licenses** just got easier! Now, you can:

* View **detailed license usage statistics** for better transparency.
* **Export license usage data to Excel** for reporting and analysis.

This ensures you have **clear insights** into license allocation and usage, helping you **optimize costs and compliance**.

***

💡 **We’d love to hear your feedback!** Let us know how these features help your workflow and what else you’d like to see. 🚀


---

# 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.aqua-cloud.io/documentation/product-updates-for-on-premise-customers/product-updates/2025/25.18.0-on-premise.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.