> 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/2024/24.101.0-on-premise.md).

# 24.101.0 - On Premise

Discover what's new in On Premise 24.101 - test run enhancements, improved localization, and key bug fixes for Jenkins, Azure DevOps, notifications, and interface layout.

*Version  24.101*

*Includes all changes since version 24.93*

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

* RQ059470 -  Enable the test run configuration fields on the 'Quick run' modal

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

* DF060390 - Installations | Issue when installing Jenkins Plugin starting from version 24.83
* DF060303 - Navigation | Broken layout in the header when enabling German language
* DF060230 - Localisation | Missing German translation on the workflow page
* DF060461 - Template and Workflow configurations | The 'Save' button is always active in the even the changes to the configuration are saved
* DF059887 - Azure Devops | Fix a typo in the description of the 'Technical user' field
* DF060140 - Notifications|  Links are not working when added to the email templates


---

# 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/2024/24.101.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.