> 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/product-updates/2025/25.67.0-on-premise.md).

# 25.67.0 - On Premise

## **Improved comment syncing between aqua and Jira: mentions made simple**

We’re excited to announce an upgrade to how comments sync between aqua and Jira — especially when it comes to user mentions.

Previously, when syncing comments with mentions, users faced inconsistent results depending on:

* whether the mentioned person existed in both systems,
* from which system the user was mentioned

This caused frustration for teams who rely on cross-system collaboration and need their comments — including who is involved — to stay clear and traceable.

With the latest aqua release, we’ve redesigned the comment sync mechanism to handle mentions smarter and more predictably. 

### **Now**:

✅ Mentions are always synced as text to aqua and Jira, even if the mentioned user doesn’t exist in the target system and it doesn't break the sync. 

✅ Mentions made in aqua are now disaplyed in Jira comment too.

\
✅ The synced comment in aqua will show Jira display name and if user is mentioned in aqua, then:

* **in aqua** \
  `@Jira display name`
* **in Jira** \
  `@ [First name] [Last name] (aqua username)`

This behavior clearly shows who was tagged in each system without breaking the sync. Even if the username is missing in the target system, the comment will still include the display name, preventing sync failures.

Users will receive an email notification only if it’s enabled in the system where they were mentioned, avoiding duplicate emails and keeping inboxes clean.

**We also plan to further improve comment syncing and enhance formatting for even better readability in the future — stay tuned for upcoming updates that will make your workflow even smoother!**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aqua-cloud.io/documentation/product-updates-for-on-premise-customers/product-updates/2025/25.67.0-on-premise.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.