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

# 25.10.0 - On Premise

Discover what's new in version 25.10 for on-premise users: autosave for manual test runs, improved defect structure, nested test case support, UI redesign, and key bug fixes.

*Version  25.10* 

*Includes all changes and bug fixes since version 24.135*

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

* RQ060419  - Test run | Autosave changes when a user run a manual test case
* RQ061512 - Reformat the structure of the defect when created from the failed/blocked test execution
* RQ061515 - Editor | Don't allow to bypass the levels when creating the ordered or numbered list
* RQ061784 - Test case | Enable adding of multiple nested test cases from the list
* RQ060703 - Tech/UI redesign | Add new design for the old error pages
* RQ059762 - Jira Plugin | button "Get aqua4Jira" should be removed from a test case/scenario page
* RQ061720 - Import | Tool to import large projects to aqua

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

* DF060258 - Remove the lines from the grids
* DF061091 - Test Scenario | Saved execution can't be finalized when it's still open on the background
* DF061665 - Toast message | No information about the file limit&#x20;
* DF060680 - Navigation | Second item open in the new tab from another page navigates the user to the previously open item


---

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