Release Notes 8.25.x

For Jira Cloud Customers (Connect on Forge Migration):

For Jira Data Center Customers (v11 Support):

Starting with QMetry v8.25.2, only custom fields that are enabled in projects for any work item type and explicitly selected by the System Administrator will sync to Custom Reporting. Additional fields must be enabled by the System Administrator upon request.

A new configuration screen under Integrations allows administrators to select the custom fields available for Custom Reporting. Previously, all custom fields were available in Advanced Query Reports by default.

This change improves the reliability of data synchronisation with the Custom Reporting database and prevents unnecessary syncing of unused fields.

For existing customers, any Jira or Azure custom fields currently used in Custom Gadgets will be automatically enabled to ensure existing reports continue to function. All other fields will be disabled by default.

QMetry v8.25.2 introduces SSL encryption for data in transit between the QMetry application and the MySQL database, enhancing data security.

QMetry v8.25.2 installations and upgrades now support MySQL v8.4.8.

The default Docker Compose version has been upgraded to v2.40.3 in QMetry v8.25. Docker Engine is now installed at the latest version available in the OS package repositories.

QMetry v8.25.2 now supports installation on RHEL 10.

QMetry v8.25.2 now supports installation and upgrade on OpenJDK 25.

A new Open API endpoint (POST /rest/requirements/latest/list) is now available to retrieve requirement data, including system fields, custom fields, synced Jira/Azure fields, and risk fields in the API response.

Add reference URLs as attachments to Test Cases and Step Executions, enabling easy linking of external evidence (e.g., logs, cloud files, or documentation) without requiring local file uploads.

The Scheduled Report email template will no longer include an editable “From” field that allows users to enter an email address. Instead, the email body will automatically include the details of the user who scheduled the report dashboard. This change improves security by preventing modification of the “Scheduled By” information and misuse of the “From” field.

A compatible version of Automation Agent v8.25.2 is included with v8.25.2. The latest agent supports OpenJDK 25 only. Users currently using the agent must upgrade their JDK and Automation Agent as part of this release.

QMetry v8.25.2 upgrades all internally used third-party libraries to their latest versions, strengthening platform security and addressing known vulnerabilities.

Jira Integration now supports JQL queries of up to 2,000 characters when integrating Jira work item types with a QMetry project, increased from the previous limit of 500 characters.

Fixed a bug that caused manual full syncs for certain Jira-integrated requirements and issues to fail, preventing some work items from syncing to QMetry.

Fixed a bug that prevented users with a Read-Only license from accessing certain modules due to incorrect permission errors.

Fixed a bug that caused Bulk Update operations on Test Cases to fail when updating test cases with existing Labels.

Fixed a bug that prevented users from viewing/adding attachments on the Test Execution screen for cross-project linked Test Cases.

Fixed a bug that caused the “Entity Key” filter on the Link Test Cases screen within Requirements to return no results when searching with a full Test Case key.

Fixed a bug that caused the "Executed At" column within the Test Case "Test Executions" tab to be sorted incorrectly instead of in chronological order.

Fixed a bug that prevented list values from appearing in Multi Lookup custom fields when placed at the end of the System Fields section in the Test Suite “Add” layout via Layout Management.

Fixed a bug that caused Lookup and Cascading Lists to incorrectly show “No records available” in the Edit List screen, especially when list names included special characters.

Fixed a bug that caused slow load times in Test Executions when opening “Available Issues” for issue/bug linking.

Fixed a bug that prevented Estimated Time from displaying for automated test cases imported via the Automation on the Test Execution screen.

Fixed a bug that caused some Azure DevOps fields to fail syncing in QMetry's Requirements and Issues modules.

Fixed a bug that caused the Test Case module/grid to remain stuck in a loading state when multiple custom field filters were applied.

Fixed a bug that caused users granted project access via SCIM to be prevented from accessing the Test Case module in projects with Risk Analysis feature enabled.

Fixed a bug that caused the QMetry panel in Jira Cloud to intermittently fail to load, display a misleading “Not Logged In” message, and temporarily hang the screen while loading Jira integration projects in the Integration tab in QMetry after the Forge add-on migration.

Fixed a bug that caused Export Test Execution Details (PDF/Word) to ignore applied filters and export all records, and display an incorrect Executed At timestamp (defaulted to 00:00:00) in the exported file.

Fixed a bug that caused test case steps beyond 15 to be cut off in Jira’s Test Case Details screen at 100% zoom.

Fixed a bug that caused intermittent false “Hourly API rate limit reached” errors even when usage was below the configured threshold.

Fixed a bug that caused the bulk test case folder copy operation to partially complete when shareable test cases were present in selected folders, resulting in those and subsequent test cases being skipped.

Fixed a bug that caused intermittent query execution errors in custom dashboard gadgets when queries contained the INTERVAL keyword.

Fixed a bug that caused Jira Fields Configuration selections made during initial Jira project setup to not be retained and requires clicking Save & Activate.

Fixed a bug that caused performance issues with slow loading of the “Available Issue(s)” tab while linking Jira issues.

Fixed a bug that caused the “Execution Archived” flag in QMetry Insights (Advanced Reports) to remain false when users archived a Test Suite, causing incorrect data in reports.

Fixed a bug that caused SQL-based custom dashboard gadgets to intermittently fail to load results when multiple gadgets using REGEXP queries were added to the same dashboard.

Fixed a bug that caused attachment downloads from Strip View redirect users back to the dashboard instead of downloading the file.