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

# 25.67.0 - On Premise

*Version  25.67.0*

*Includes new features, improvements and bug fixes since version 25.56.0*

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

* **RQ065783** – Jira sync | Comments | Improve synchronization behavior when users are mentioned

***

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

* **DF064727** – Azure or Jira sync | After deleting the sync, the dependency does not disappear
* **DF064729** – User administration | Selection is lost if search fits to a user on another page
* **DF064730** – User administration | The selection of the user doesn't reset
* **DF065652** – Jira sync | Comments | Creator and mentioned users in comments aren't displayed correctly
* **DF065807** – The project assignment email is sent in English when German is a main language
* **DF066136** – Project configuration | Can't add a single selection field into some templates
* **DF064694** – The test case bypasses the 'required' setting for expected result when saving


---

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