> 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.26.0-on-premise.md).

# 25.26.0 - On Premise

Discover what’s new in aqua 25.26.0 for on-premise: enhanced test scheduling, new password visibility controls, improved project import, and key bug fixes since 25.18.0.

*Version  25.26.0*

*Includes all changes and bug fixes since version 25.18.0*

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

* RQ059363 - Test scenario | Automation | Schedule executions of the test scenarios in a web client
* RQ061420 - Password | server configuration option to hide "make password visible" option from login/reset password modal
* RQ062146 -  Project import tool | Support showing test scenario value on navigation to which test cases belong

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

* DF062938 - Import from Testrail | Testcase type of Exploratoy Session has no step when importing to aqua
* DF060747 - Views | It is impossible to select a project when copying View if there are fewer than 12 projects
* DF062974 - File downloads still request storage directly


---

# 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.26.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.