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

# 25.91.0 - On Premise

## 🔁 More Flexible Jira Sync

We've brought back and expanded several popular options for Jira sync direction, giving you more control over how tickets move between systems. You can now choose from five modes:

* Bi-directional
* From Jira to aqua only *(recently released)*
* From aqua to Jira only *(recently released)*
* Bi-directional, but only for tickets created in aqua *(<mark style="color:orange;">restored</mark>)*
* Bi-directional, but only for tickets created in Jira *(<mark style="color:orange;">restored</mark>)*

These options help tailor the sync behavior to match your team’s exact workflow—whether you start in aqua, Jira, or both.

{% hint style="warning" %}
Please note that you need to update your Jira sync set up if you want to use:&#x20;

* Bi-directional, but only for tickets created in aqua&#x20;
* Bi-directional, but only for tickets created in Jira&#x20;
  {% endhint %}

## 🛠️ Agile View & Ticket Improvements

We've made several smaller, but impactful improvements across the platform. On Agile page, you’ll now see a **dedicated "Story Points" column**, making it easier to understand the size of tickets at a glance and sort them more efficiently.

You can also now **delete and archive tickets** directly from the Agile page and the Scrum board—saving you extra clicks and keeping your boards clean.

## 📁 Enclosure Settings for Cleaner Jira Sync

On the project management side, we’ve introduced a new option to **hide adding multiple enclosures at the project level**. This is especially useful for teams syncing with Jira, as Jira currently supports only one enclosure (the description field) for sync. This change helps keep things clean and avoids confusion when syncing across systems.

➡️  Read more [here](/documentation/items/defects-management/defects/option-to-hide-enclosures.md)

***

Thanks for all your feedback—it’s what drives every improvement we make. These updates are all about making aqua work better for you. As always, stay tuned for even more enhancements on the way.


---

# 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/product-updates/2025/25.91.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.