> 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/release-notes/2025/25.36.0-on-premise.md).

# 25.36.0 - On Premise

Discover what's new in aqua 25.36.0 On Premise: support for TestRail suites import, Confluence Data Center, Jira ticket linking, plus key bug fixes for improved stability.

*Version  25.36.0*

*Includes bug fixes since version 25.33.0*

<mark style="color:green;">**New requirements and improvements:**</mark>&#x20;

* RQ063533 - Importing from Testrail | Support import of the test suites
* RQ063141 - Integrations | Confluence | Support Confluence Data Center version
* RQ063046 - Integrations | Confluence | link pages to aqua tickets using URL
* RQ061686 - Jira Sync | Show link to aqua ticket in Jira

<mark style="color:red;">**Fixed defects:**</mark>&#x20;

* DF063135 - log file | incorrect password is shown in plain text in the logs
* DF063545 - Project configuration | Date field settings issue
* DF062909 - Login page appears after a session timeout despite SSO
* DF063597 - Test scenario scheduler | "something wen't wrong" error when setting the date&#x20;


---

# 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/release-notes/2025/25.36.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.