# 26.xx - public and private cloud
*Includes improvements and bug fixes since version 25.127.0*
{% hint style="info" icon="message-minus" %}
Version 26.xx delivers improvements to Jira integration, Azure DevOps sync, and dashboards, along with a range of defect fixes.
{% endhint %}
## 🔄 What's Changed
### :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
### 🔧 Platform Fixes and Improvements
#### 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
#### 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.
---
# Agent Instructions: 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:
```
GET https://docs.aqua-cloud.io/documentation/product-updates-for-public-and-private-clouds-customers/product-updates/2026/26.xx-public-and-private-cloud.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.