Release Notes 8.28.x

Build 8.28.2.2 - Release Date: 2026-10-15

Summary: New REST API and Bug Fixes

New REST API

Added the following API.

API

Endpoint

What it does?

Get API call quota status

GET /rest/admin/apiquota/status

Returns the hourly and daily Open API call limits and consumption for your QMetry instance.

Bug Fixes

  • Fixed a bug that caused the project filter on Custom Dashboard gadgets to display “null” instead of the project names when the capitalization of the project filter field differed from the global filter.

  • Fixed a bug that caused Jira issues moved from a non-integrated project into an integrated project to be imported into QMetry even when they did not satisfy the configured JQL filter criteria.

  • Fixed a bug that caused Jira work items to fail to import into QMetry when the Jira project name contained an apostrophe or special character.

Build 8.28.2.1 - Release Date: 2026-10-08

Summary: New Features, Enhancements & Bug Fixes

This release introduces a series of UI and usability enhancements to QMetry, providing a smoother, faster, and more intuitive user experience. Key improvements include an upgrade to Angular 21, always-visible actions, faster Test Case folder navigation and Test Step editing, streamlined navigation and form controls, and enhanced Rich Text Editor capabilities.

Additionally, QMetry introduces two new features for Jira Data Center customers, offering greater control over Jira connectivity. These features help organizations meet compliance and regulatory requirements by enabling stricter data separation and access restrictions.

New Features

QMetry Integration for Jira Data Center

  • Connect Multiple QMetry On-Premise Instances to One Jira Data Center instance.

    • QMetry now supports organizations that run separate QMetry instances for compliance or data-separation rules. Each QMetry instance keeps its test data separate while connecting to the same Jira Data Center, so QMetry fits easily into complex enterprise setups.

    • How it works:

      • Each Jira project can be linked to only one QMetry instance.

      • Once a Jira project is linked to a QMetry instance, no other instance can select it.

      • When multiple QMetry instances are connected, Jira Data Center administrators must choose which projects are available for QMetry integration (see the next feature).

  • Choose Which Jira Projects Can Connect to QMetry

    • Jira Data Center administrators can choose which Jira projects are allowed to connect to QMetry.

    • Some Jira projects contain sensitive information that should not be linked to QMetry. This feature helps organizations meet compliance and data-governance requirements.

    • How it works: Jira Data Center administrators can choose between two options:

      • All Projects: Every Jira project is available for QMetry integration. This is the default when a single QMetry instance is integrated with Jira, and it is available only in that setup.

      • Selected Projects: Only the projects selected by the administrator are available for QMetry integration, and all other projects remain hidden. This option is available whether one or multiple QMetry instances are integrated with Jira. With multiple QMetry instances, it is the default and the only available option.

    • Existing customers with a single QMetry instance stay on All Projects, so current integrations continue to work as is, with no action required.

Compatibility and Prerequisites

To ensure compatibility with QMetry 8.28.2.1, customers who use Jira Data Center must use the following versions.

Component

Required Version

Jira Data Center

10.x or 11.x

QMetry Integration for Jira app (on Jira 10.x)

v2.4.5_jira10

QMetry Integration for Jira app (on Jira 11.x)

v2.4.5

  • Customers who use the Azure DevOps extension must use QMetry Test Management Extension v1.2.2.

  • QMetry Integration for Jira v2.4.5 adds support for Jira Data Center 11.3.11.

Enhancements

QMetry User Experience and UI Enhancements

Best Practice: Reload the browser tab containing QMetry to ensure all changes are fully applied and visible.

Framework and Security

UI Framework Upgrade

The QMetry UI now runs on Angular 21. The upgrade improves application performance and provides a foundation for upcoming UI enhancements.

Security Enhancements

The Angular 21 upgrade includes the latest security fixes, addressing known framework vulnerabilities and strengthening protection against common web threats such as cross-site scripting (XSS).

Forms and Fields Enhancements

Checkboxes for Multi-Select Fields

Multi-select fields now use checkboxes, allowing users to view and change selected values directly in the list.

Filter Panel Updates

Filter panels across QMetry have been enhanced with clearer field labels and easier value selection.

  • Improved label placement to make fields easier to identify.

  • List and dropdown controls have been resized for easier selection.

Manage Fields Updates

Manage Fields now separates User-Defined Fields and System-Defined Fields into two tabs for easier access and management.

Date Picker Updates

The date picker now provides an intuitive interface for selecting a single date or date range.

Rich Text Editor Enhancements for Large Text Fields

New Formatting Options

The Rich Text Editor has been enhanced with additional formatting options, making it easier to create and organise rich content directly within large text fields without using the Source Edit for HTML editing.

New formatting options include:

  • Heading Styles

  • Font Size Selection

  • Text Colour and Highlight

  • Indent and Outdent

  • Code and Code Block

  • Nested Ordered and Unordered Lists

  • Clear Formatting - The existing option has been enhanced to remove text-level formatting while preserving the structure of tables and lists. Code blocks are converted to normal text.

Rich Text Editor Performance

Table creation has been optimised to use less storage, reducing database usage and improving performance for large tables.

Deprecation of Source Edit

The Source Edit option in the Rich Text Editor toolbar is now deprecated and will be removed in a future release. The new formatting options support common formatting tasks that previously required editing the underlying HTML.

Additional Enhancements & Behaviour Changes

Audit and change log enhancements

Audit and change logs now clearly show the differences between old and new values, making it easier to understand what changed.

Help menu updates

Feedback and About are now available under the Help icon, providing a single place to submit feedback and view product and version information.

Execution screen: Expand All and Collapse All

The Expand All and Collapse All options, which expand or collapse steps across all Test Runs in a view, are now disabled when the view contains more than 50 Test Runs. This ensures the Execution screen remains fast and responsive when working with large views.

Custom XML Automation Template Enhancements

The Custom XML Automation Template, introduced in QMetry 8.27 to enable teams to import automation execution results from custom or proprietary XML report formats without writing custom import scripts, now supports the following options:

  • Default Execution Status: Set a default status such as Passed, Failed, Not Applicable, or Not Run when no status mapping is found in the XML for a Test Run. A mapped status takes precedence. The default status is Passed unless explicitly changed.

  • Aborted and Skipped Status Mapping: The aborted and skipped tags in automation results can now be mapped to custom execution statuses. These statuses must first be added as custom execution statuses in the project.

Copy Test Case Steps Workflow Improvements

  • The Copy Steps from Existing Test Case screen now retains and automatically applies the most recently used filter criteria, making it quicker to locate relevant test cases without reconfiguring search parameters each time.

Performance Enhancements

  • Overall performance improvements give user a smoother experience throughout QMetry Test Management.

  • Improved performance while loading the Test Cases, Requirements, and Test Suites modules in projects with large data sets and nested folder structures.

  • Test case folder performance: The Test Case folder structure now loads and navigates faster, especially in large projects with deep folder hierarchies.

  • Test step editing performance: Editing Test Case steps is now faster, with reduced lag and wait times.

  • Inline editing performance: Inline editing has been optimised across different field types, making it faster and smoother to edit fields directly within the UI.

API Changes

  • Open API support for parameterized Test Cases: QMetry Open APIs now support assigning and managing parameter values for parameterized test cases in Test Suite executions, including linking Data Grid combinations or manually providing parameter values.

    Method

    Endpoint

    Purpose

    POST

    /rest/testcases/list/forTS

    Fetches Test Cases linked to a Test Suite, including whether each Test Case is parameterized ( true / false) and, where applicable, its Data Grid status (Has Values/Empty) and Data Grid Mapping ID.

    POST

    /rest/testcases/getParamDetails

    Fetches the parameter IDs for a parameterized Test Case associated with a Test Suite.

    POST

    /rest/datagrid/getSelectedParameterGrids

    Fetches compatible Data Grids that contain all parameters used by the parameterized Test Case.

    POST

    /rest/datagrid/linkCombination

    Links a selected Data Grid and its parameter combinations to a Test Case in a Test Suite.

    GET

    /rest/datagrid/tctsDataGridValue/{tctsDataGridMappingID}

    Fetches the parameter values currently assigned to a Test Case in a Test Suite.

    POST

    /rest/datagrid/saveTcTsDgValues

    Adds or updates parameter values assigned to a Test Case in a Test Suite.

    DELETE

    /rest/datagrid/tctsMapping/{tctsID}

    Removes the Data Grid mapping and all associated parameter values from a Test Case in a Test Suite.

  • New REST APIs:

    QMetry introduces two new REST APIs that let user fetch multiple Test Cases, and project and execution details, in a single request.

    Method

    Endpoint

    Purpose

    POST

    /rest/testcases/bulk/fetch

    Fetches multiple test cases in a single request.

    Simplifies automation and integration workflows.

    POST

    /rest/admin/getDetails

    Fetches project, release, cycle, platform, and test suite details in a single request.

    Reduces the need for multiple API calls

Bug Fixes

  • Fixed a bug that incorrectly reported the hourly API quota as exhausted, causing valid API requests to be rejected and usage data to be reported incorrectly in system reports.

  • Fixed a bug that prevented rich text formatting such as bold, italic, and underline from being applied to Large Text fields in Safari browser.

  • Fixed a bug that prevented users with the "Reports Modify" permission from sharing a gadget on the My Gadget screen when the All Dashboards and Gadgets Modify permission was not enabled.

  • Fixed a bug that caused recently assigned projects to not appear in the Global Filters' project dropdown in Custom Dashboards and System Reports, despite users having valid access.

  • Fixed a bug that prevented users assigned the System Read-Only role from generating an OpenAPI key, even when OpenAPI View and Modify permissions were enabled for the role.

In this section:
© 2026
Publication date: