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 (restored)

• Bi-directional, but only for tickets created in Jira (restored)

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

Please note that you need to update your Jira sync set up if you want to use:

• Bi-directional, but only for tickets created in aqua

• Bi-directional, but only for tickets created in Jira

🛠️ 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

---

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.