> 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-public-and-private-clouds-customers/product-updates/2026/26.29-public-and-private-cloud.md).
# 26.29 - public and private cloud
*Includes improvements and bug fixes since version 25.127.0*
{% hint style="info" icon="message-minus" %}
Version 26.29 delivers improvements to Jira integration, Azure DevOps sync, and dashboards, along with a range of defect fixes.
{% endhint %}
## π What's Changed
### π§ aqua Intelligence β A New Name, A Stronger AI
aqua AI Copilot is now aqua Intelligence β and it's more than a rename. The underlying AI platform has been rebuilt for better performance and reliability, so everything you already use works faster and more consistently.
*(Image above: Configure aqua Intelligence settings page)*
#### Enhanced Knowledge Base
Managing your knowledge base files is now faster and more flexible:
* More **file types** supported β **PDF**, DOCX, **XLSX**, **Markdown**, and TXT are all accepted
* Larger file limit β upload files up to **100 MB**, up from 10 MB
* **Search** your uploaded files β find what you need without scrolling through the full list
* Live **processing** **status** β see whether a file is Processing, Ready, or has an Error in real time, no more waiting for an email confirmation
{% hint style="warning" %}
**Action required: re-upload your knowledge base files**
Rebuild of the aqua Intelligence platform brings significantly better performance and more powerful generation. With this improvement β previously uploaded knowledge base files will not be carried over automatically.
After updating, you will need to **re-upload your files to the global or project knowledge base**.
If you need to know what was previously uploaded, please contact our support team at .
{% endhint %}
Read more on the knowledge base benefits here [Knowledge Base with aqua Intelligence](/documentation/aqua-intelligence/knowledge-base-with-aqua-intelligence.md)
The chat input also shows a live character counter, with a minimum of 35 characters when a file is attached or 4 characters for text-only messages.
### :e-mail: Jira Plugin Migrated to Atlassian Forge Platform, With Improved Statistics
The Jira Plugin for Cloud has moved from the Connect framework to Forge, bringing improved security and long-term compatibility. We improved how test cases and test scenarios appear in the plugin, giving you clearer statistics and better visibility into your testing progress directly from Jira.
#### **Connect Multiple aqua Environments (Data Center):**
Until now, the Jira Plugin could only be connected to a single aqua instance. For the Data Center, you can now configure multiple server connections that are linked to specific Jira projects, independently named, and manageable without affecting the others.
#### Clearer Test Status at a Glance (Data Center):
If you are using the Data Center Plugin, we redesigned the way test results appear inside your Jira tickets. Instead of scrolling through a long list of individual execution entries, you now see a clean, collapsed summary showing the current status and a test case count. Expand it to see per-test-case results with dates and testers. For test scenarios, the view aggregates statistics across all contained test cases, making it easy to understand testing progress without ever leaving Jira.
#### Platform Migration to Forge:
We've completed the first step in adopting Atlassian's Forge platform, the modern foundation that Atlassian is building the future of its app ecosystem on. This ensures the aqua Jira Plugin for Cloud stays aligned with the direction Atlassian is heading and remains on a fully supported, forward-looking path. Nothing changes for you in terms of how the plugin works today.
#### Optimised Request Handling:
We've improved how the plugin communicates with aqua, reducing unnecessary requests and making the integration more efficient and stable under load.
### π Jira Sync Improvements
Jira sync fixes in this release:
* Jira sync keys mapping logic has been improved, resolving an error that previously prevented creating a new sync
* Jira sync no longer fails to update deleted field values in aqua
* Jira sync no longer hangs due to archived version handling
### πAzure DevOps Sync: Custom Rich Text Fields Now Supported
Previously, the Azure DevOps sync covered a fixed set of fields. Any additional multi-line fields in Azure DevOps, such as Repro Steps, System Info, or Acceptance Criteria, had to be maintained manually in both systems.
With this release, custom Rich Text fields now sync bidirectionally between aqua and Azure DevOps. The sync works based on name matching: when a multi-line field in Azure DevOps has exactly the same name as an RTF field in aqua, the two fields sync automatically. No additional configuration is needed. New matching fields are picked up on each sync call, so there is no need to reconfigure the sync when fields are added or changed.
*(Image above: View of Bug item type in Azure DevOps which has a Repro Steps field to be synchronized)*
*(Image above: creating a custom RTF βRepro Stepsβ in aqua)*
**How to set it up:**
To synchronise the item type Bug in Azure DevOps with a field called "Repro Steps":
1. In your aqua Defect template, create a custom RTF field named "Repro Steps" (the name must match exactly)
2. Once created, the field will sync automatically for all Bugs mapped to Defects
The same applies to any other multi-line field. Identify which Azure multi-line fields you want to sync, create matching custom RTF fields in aqua with the exact same names, and sync will happen automatically.
**Azure sync fixes in this release:**
* Sync errors that occurred after resetting an Azure sync have been fixed
* An issue where it was not possible to save a new sync when one of the sync items was disabled has been resolved
### π Smarter Test Coverage Reporting in Dashboards
Previously, dashboard charts for test scenarios showed only the overall scenario-level status. This created a reporting problem. For example, if you had five test scenarios and one of them was complete, the dashboard showed 20% completion, regardless of how many test cases each scenario contained. A scenario with 20 test cases counted the same as one with 5, which gave leadership and stakeholders an inaccurate picture of actual testing progress.
*(Image above: new parameter when creating/editing a dashboard)*
With this update, dashboards can now display metrics based on individual test case execution status within test scenarios. The metrics aggregate the execution results of all test cases contained across the selected scenarios. Now, based on the example above, a dashboard would show 50% completion (20 out of 40 test cases), not 20%.
Clicking into the chart drills down to show individual test case results and which scenario each test case belongs to. Existing dashboard configurations that use scenario-level status continue to work unchanged.
*(Image above: drill-down view of a dashboard with test scenarios grouped by test case execution status)*
**Dashboard fixes in this release:**
* Dashboard filter no longer cuts off the Apply and Save buttons
* Calendar weeks in stacked bar charts are now displayed correctly
### π Password Expiration Policy (Private Cloud)
aqua now provides administrator-controlled password expiration policies, available for private cloud and on-premise installations only (not available on aqua SaaS). This is particularly relevant for regulated industries such as financial services, insurance, or the public sector, where periodic credential renewal is mandated by compliance frameworks.
(I*mage above: Set new password screen shown when a password has expired, with validation message and password requirements)*
**What administrators can configure:**
* Password expiry period: how frequently users must set a new password
* Password history: prevents reusing recent passwords
* Account lockout: restricts access after repeated failed login attempts (5 attempts and 30 minutes by default)
All three settings are disabled by default and can be enabled independently. A minimum password age of 24 hours also applies, preventing rapid password cycling, except for token-based resets.
**How it affects users:**
When a password expires, the user is prompted to set a new one on their next login and cannot access the app until they do. The new password cannot be a trivial variation of the old one (for example, Secret123 to Secret124). If this policy is enabled for the first time, all existing users are treated as expired immediately.
**Exemptions:**
Technical users (API, sync integrations) and externally authenticated users (AD, LDAP, SAML) are not subject to expiration. Administrators can also manually exempt individual users, such as Jira Plugin accounts, via User Administration.
**Known limitation:** Desktop client users whose password has expired must log in via the web client first to change it, after which desktop login works again.
### π§ Platform Fixes and Improvements
#### Performance and infrastructure
* Save actions in modules such as user administration, template configuration, and workflow and field rules no longer take an unexpectedly long time to complete
* The Microsoft SQL Server ODBC driver has been updated to address known security vulnerabilities (on-premise)
#### Test cases and test execution
A few rough edges in the testing workflow have been polished away:
* Copying a test scenario no longer strips labels from the original
* Resuming an in-progress execution no longer shows a confusing "Item not found" error message
{% hint style="warning" %}
**Known issue: generating multiple Gherkin test cases with AI**
When generating multiple test cases with BDD as the output format, only one test case is produced and it may not be correctly structured as Gherkin.
A fix is already in progress and will be delivered in a patch release shortly after this one.
Generating a single Gherkin test case works as expected, as does all other test case generation across all input types and output formats.
{% endhint %}
#### Templates and Custom Fields
Configuring custom fields in the template editor is now more predictable. Weβve also resolved several issues that caused settings to silently revert.
* Decimal places no longer reset after saving
* Date fields of the Long Date and No Time types now save correctly
#### User and Workflow Administration
A handful of fixes for teams managing users and workflows:
* Bulk password reset is back in the actions menu for selected users
* The user table scales correctly when paginating
* Attempting to set an invalid username now gives clear feedback instead of silently discarding the change
* Status field values can now be renamed without errors
### π‘ What This Update Means for You
Teams working with Jira or Azure DevOps will see fewer sync gaps and more data flowing automatically between systems. Dashboard users get a more accurate picture of test coverage without needing to check multiple views.
Ways to use the new features:
1. **Syncing with Azure DevOps?** If your Azure bugs have fields like Repro Steps, System Info, or Acceptance Criteria, you can now create matching RTF fields in aqua and have them sync automatically, without maintaining them manually in both tools.
2. **Working across aqua and Jira?** The Jira Plugin for Data Center now includes improved statistics representation for test cases and test scenarios.
3. **Reporting coverage to stakeholders?** Open your dashboard and select Test Scenarios as the data source to see aggregated test case execution results across scenarios, giving a more accurate coverage picture in one view.
***
For full list of changes, please see the Release Notes [26.29 - public and private cloud](/documentation/product-updates-for-public-and-private-clouds-customers/release-notes/2026/26.29-public-and-private-cloud.md)
---
# 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-public-and-private-clouds-customers/product-updates/2026/26.29-public-and-private-cloud.md?ask=&goal=
```
`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.