Release Notes

Release Notes

Build 8.23.0 - Release Date: 2025-10-18

Summary: New Features, Improvements and Bug Fixes

 

New Features

Test Suite Features and Enhancements

  • The individual Test Suite copy operation now supports copying for a specific combination of Release, Cycle, and up to five Platforms, with additional options to include execution status, latest linked test case versions, assignee, and planned dates. For e-signature-enabled projects, the only option available is to copy the latest approved versions of linked test cases.

  • The Bulk Copy of Test Suites is enhanced to support two additional options -

    • Copy for a specific Release and Cycle combination, with options to include existing Platforms and the latest linked versions of test cases.

    • Copy for a specific combination of Release, Cycle, and up to three Platforms, with the option to include the latest linked versions of test cases.

Test Execution Features and Enhancements

  • Bulk operations on the execution screen now include a new option to add execution comments for multiple test cases. Testers can also add execution comments when updating execution statuses in bulk.

  • Bulk operation to update assignee on the Execution Screen now allows unassigning testcase executions in bulk.

  • Bulk operations on the Execution Screen now run in the background for improved performance. Users can track the progress of these operations under the "Scheduled Tasks".

Project Enhancements

  • Introduced a project setting that lets admins toggle off the option for users to automatically sync executions with the latest version when creating a new test case version. This setting is available only for projects without eSignature enabled and helps preserve execution details for prior versions by preventing unintentional force-sync during creation.

Cascading Field Enhancements

  • Moving or copying test assets to another project will now include cascading-type custom fields and their selected values, ensuring all data remains intact during these operations.

  • Cascading lists and their values can now be copied or imported between projects, making list management easier for project administrators.

QMetry Insights Enhancements

  • Enabled support for the WITH clause in SQL queries, empowering users to build custom reports using Common Table Expressions (CTEs) within the Advanced Query Reports module.

  • QMetry Insights (Visual and Advanced Query modules) now supports displaying cascading fields as columns in custom reports, whether the fields are created in QMetry or synced fromJira work items.

 

Miscellaneous Enhancements

  • The Assignee and Owner dropdowns now display the logged-in user at the top for quickerself-assignment and easier filtering of items assigned to themselves.

  • Introduced a shortcut to quickly assign the current user as the owner of test assets while creating or editing them.

 

QMetry Integration for Jira app Upgrade

  • To ensure compatibility with QMetry Release v8.23, customers using Jira Data Centre must upgrade the QMetry Integration for Jira app to version 2.3.7 for Jira 10 or to version 2.3.7_jira9 for Jira 9 and earlier.

 

Exploratory Testing Extension Upgrade

  • Users must upgrade their QMetry Exploratory Testing browser extension to the latest version to ensure compatibility with QMetry Release 8.23. The latest versions of extensions are:Chrome 1.2.9, Firefox 1.1.2, and Edge 1.0.8.

 

Bug Fixes

  • Fixed a bug that prevented users with Project Collection Administrator permissions inherited through a group from configuring the "QMetry Test Management" extension in Azure DevOps.

  • Fixed a bug that caused bulk move and archive operations to fail for test cases imported through feature files (BDD import).

  • Fixed a bug that caused the Execution Status dropdown to extend off-screen when expanding a test execution near the bottom of the browser window.

  • Fixed a bug that caused child test cases from subfolders to be excluded when filtering test cases by a parent folder path in the Test Suite.

  • Fixed a bug that caused SQL queries in Advance Query Reports using CTE with UNION to bypass project-level permissions.

  • Fixed a bug that caused users to be logged out and redirected to the login page when opening Test Suite, Test Case, or Requirements folder URLs in a new Firefox tab, affecting all open QMetry tabs.

  • Fixed a bug that caused all test cases to be exported, ignoring applied filters, when using the “Export All Records” option in the Test Cases module.

  • Fixed a bug that linked multiple versions of a test case to a new Test Suite, including all previously selected versions instead of only the final selected version. (edited) 

  • Fixed a bug that caused Jira user authentication to fail for QMetry integrations when using Jira Cloud with a custom domain URL, impacting the ability to add attachments and post comments to Jira issues from QMetry.

  • Fixed a bug that caused exported test suite execution documents (PDF/Word) to fail downloading when the associated Release or Cycle name contained square brackets “[ ]”.

  • Fixed a bug that caused the QMetry panel in Jira to occupy excessive space on Jira pages when no test cases were linked or the BDD section was disabled, causing inconvenience due to unnecessary scrolling.

 

Build 8.22.1 - Release Date: 2025-09-04

Summary: New Features, Improvements and Bug Fixes

 

New Features

Test Case and Requirement Module

While creating test cases from the Requirement and Test Case modules, users can now plan and execute them within the same flow, enabling a streamlined end-to-end workflow.

With this feature, users can perform the following actions:

  • From the Test Case module > Create Test Case screen:

    • Link the test case to the requirements to establish traceability.

    • Link the test case to an existing Test Suite or create a new Test Suite for planning and execution.

    • New Test Suites created in this flow are automatically associated with the release and cycle defined in the originating test case.

  • From the Requirement module, while creating a test case:

    • Link the test case to an existing Test Suite, or create a new Test Suite for planning and execution.

    • The Test case and Test Suite created during the flow are automatically associated with the release and cycle defined in the originating requirement.

Once a Test Suite is created or linked, users can directly execute test cases within the same flow.

Key Benefits:

  • Unified end-to-end workflow from requirement → test case → execution → issues in a single flow.

  • Automatic association with release and cycle for traceability.

  • Reduced manual effort by eliminating cross-module navigation.

 

Jira Integration

Create Test Case and Test Suite options are introduced within the Jira Work Items > Test Case section. These options redirect users with authorised access to QMetry, allowing them to create test cases and test suites directly from Jira. This enhancement boosts productivity by reducing tool switching, simplifying navigation, and strengthening traceability between Jira and QMetry.

  • Create Test Case and Test Suite options are available for all work item types integrated with the QMetry Requirement module.

  • The Create Test Case option is available for all work item types integrated with the QMetry Issue module.

  • The created test case gets automatically linked to its originating work item. Similarly, the created test suite gets linked to all test cases associated with the originating requirement work item.

  • To ensure compatibility with QMetry Release v8.22.1, customers using Jira Data Centre must upgrade the QMetry Integration for Jira app to version 2.3.5 for Jira 10 or to version 2.3.5_jira9 for Jira 9 and earlier.

 

Azure DevOps Integration

  • Create Test Case and Test Suite options are introduced in Azure DevOps Work Items > QMetry Test Coverage. These options redirect users with authorised access to QMetry, allowing them to create test cases and test suites directly from Azure DevOps. This enhancement boosts productivity by reducing tool switching, simplifying navigation, and strengthening traceability between Azure DevOps and QMetry.

    • Create Test Case and Test Suite options are available for all work item types integrated with the QMetry Requirement module.

    • The Create Test Case option is available for all work item types integrated with the QMetry Issue module.

    • The created test case gets automatically linked to its originating work item. Similarly, the created test suite gets linked to all test cases associated with the originating requirement work item.

  • To ensure compatibility with QMetry Release v8.22.1, the QMetry Test Management Extension for Azure DevOps must be installed or upgraded to version 1.0.2

 

Bug Fixes 

  • Fixed a bug that generated blank PDFs when exporting Custom and System Dashboards.

  • Fixed a bug that caused certain graphical charts or gadgets on the QMetry Custom Dashboard to display unrounded floating-point values instead of properly formatted two-decimal-place values.

  • Fixed a bug where filtering Jira issues by "Status" in QMetry for Jira-integrated projects returned empty results despite existing matches.

  • Fixed a bug where filtering requirements by “Created System” (QMetry or Jira) in the Requirements module returned no results.

  • Fixed a bug where console logs were not being captured in the QMetry Exploratory Testing Plugin on the latest Chrome browser.

  • Fixed a bug in Bulk Edit operations for test suites, where the "Skip Duplicate Linkage" option failed to prevent duplicate test case linkage to test suites.

  • Fixed a bug that caused requirement module to become unresponsive when users navigated from any module with Jira filters applied.

  • Fixed a bug where requirements synced from Jira were not auto-organized into the correct folder hierarchy in QMetry when the Fix Version was assigned via Jira automation.

  • Fixed a bug that caused users to encounter an error when setting execution status for test steps.

  • Fixed a bug that caused failures when uploading JUnit test result ZIP files through the Jenkins plugin with Automation Hierarchy 2, leading to unexpected errors and incorrect test case counts.

  • Fixed a bug that caused test case imports to ignore relative folder paths and create test cases in incorrect locations.

  • Fixed a bug that caused the Screens tab to freeze when exporting Exploratory sessions having more than 300 captures to PDF or Word.

  • Fixed a bug that prevented Jira issues from syncing and importing to QMetry due to changes in the underlying Jira API in Atlassian Jira Cloud.

  • Fixed a bug that prevented the "QMetry Configuration" page from loading on Jira Cloud instances with a custom domain, which blocked the QMetry<>Jira integration from establishing a connection.

     

Build 8.22.0.1 - Release Date: 2025-08-04

Summary: Bug Fixes

  • Fixed a bug that caused the Test Case module to become unresponsive in projects with a large volume of test assets.

  • Fixed a bug that caused the “Fetch List for Bulk Operation" API to return a 400 error when retrieving test cases for bulk operations.

  • Fixed a bug that caused an error when linking test cases via the “Link Test Cases from Requirement” option within the Test Suite module.

 

Build 8.22.0 - Release Date: 2025-08-02

New Features in Test Case Module

  • Test Cases Reusability Across Multiple Folders: A single test case can now be associated with multiple folders within the same project. This feature allows users to reference the same test case (identified by its unique key) across different folders, within the same hierarchy or across different hierarchies, without creating duplicates.

  • Folder-Level Test Case Sequencing: Users can now define a custom order for test cases within each folder. The sequence is maintained uniquely per folder, enabling teams to organize test cases according to specific scenarios or execution flows. The Order column appears in the test case grid only when Include Entities from Sub-Folder option is disabled.

 

Enhancements and Workflow Updates in the Test Case Module

The following workflow updates have been introduced in the Test Case module to enable test case reusability and folder-level sequencing. These enhancements simplify test case organization, enhance folder management and provide better control over archived assets.

  • The Project Root Folder now displays all active test cases by default. Any newly created test case will be saved under the “Project Root Folder”, in addition to the selected folder. The “Include Entities from Sub-Folder” view now applies only to subfolders and not to the Project Root Folder.

  • A new filter, Show Only Test Cases Not Assigned to Any Folder, has been added to enable users to quickly identify test cases that are not associated with any folder.

  • Archiving a test case now automatically removes it from all linked folders. These test cases are excluded from folder-level counts and no longer appear alongside active test cases. A new dedicated filter, Show Only Archived Test Cases, is introduced to enable users to locate and manage archived test cases. As part of this release, all previously archived test cases in the projects will be disassociated from their respective folders. For reference, the test case change log will record the original folder path.

  • Archiving a folder will now archive only the folder itself and not the test cases it contains. All test cases within the folder will be disassociated from it upon archiving. During folder archiving, users now have the option to move the test cases to another folder. If the test cases also need to be archived, they must be archived separately. A separate filter, Show Archived Folders, is introduced to enable users to view and manage archived folders.

  • The folder path navigation breadcrumbs at the top of the Test Case details screen now display the folder from which the test case is being accessed. This ensures accurate context when a test case is referenced across multiple folders. Sharing the link to the test case will open it from the Project Root Folder.

  • Deprecated Features:

    • Sorting by folder path is no longer supported across application screens, as test cases can now reside in multiple folders.

    • The test case count is no longer displayed next to the project root folder to prevent misrepresentation, as test cases can now reside in multiple folders.

 

Improvements and Changes to QMetry Insights (Custom Reports)

Visual Reports Changes

  • The Test Case Entity table in Visual Reports now includes two new columns: Test Case Folder Name and Test Case Folder Archived, enabling users to generate reports based on folder names and easily filter out archived folders.

  • Action Required - Existing custom gadgets built using Visual Reports, having the “Test Case Folder ID” or “Test Case Folder Path” fields or filters, must be updated, as they will currently display incorrect data. To maintain accurate results, simply edit the gadget, remove these fields or filters, and re-add them to reflect the latest updates.

Advance Query Report Changes

  • A new table, testcasefolder, has been introduced to store test case folder information, including folder name, path, ID, and other related details.

  • Action Required - Existing custom SQL gadgets created using Advanced Query Reports that include the fields or filters “testcases.folderName”, “testcases.folderPath” , or “testcases.tcFolderID” should be updated, as they will currently display incorrect data. To maintain accurate results, update the queries to fetch or filter test case folder-related data by joining data from the new testcasefolder table.

Jira Integration Add-on Upgrade

  • As part of Release v8.22, compatibility requires upgrading the QMetry Integration for Jira app to version v2.3.4 for customers using Jira 10, and to v2.3.4_jira9 for those using Jira 9 or earlier. For Jira Cloud customers, the app gets automatically upgraded.

Azure DevOps Integration Add-on Upgrade

  • As part of Release v8.22, the QMetry Test Management Extension for Azure DevOps must be installed or upgraded to version 1.0.1 to ensure compatibility.

 

Miscellaneous Enhancements

  • The maximum field length for both Username and Alias is increased to 256 characters to support longer names.

  • The “Generate SQL reports” and “QI Search: Ask me Anything” AI features have officially transitioned from Beta to General Availability (GA)!

 

Bug Fixes

  • Fixed a bug that caused only the filtered labels to be exported when using the “Export All Records” option after applying a label filter in the Test Case module.

  • Fixed a bug that caused no results to be returned when applying filters in the Custom Shared Dashboard.

  • Fixed a bug that caused errors when uploading attachments with uppercase file extensions (e.g., .JPG, .PNG) in the attachments section.

  • Fixed a bug in the Test Suite module where the Test Cases tab showed a limited number of test cases due to fixed height not using full screen space.

  • Fixed a bug where the “Change Test Case Order” pop-up in the Test Suite module displayed fewer test cases due to a fixed height, despite available screen space.

  • Fixed a bug that caused the color modification option to be unavailable for Line charts in QMetry Insights when configuring custom reports.

  • Fixed a bug where navigating into a test suite redirected users back to the test suite grid instead of the execution screen. 

  • Fixed a bug that generated blank PDFs when exporting Custom and System Dashboards.

 

Build 8.21.0.2 - Release Date: 2025-07-16

Summary: Bug Fixes

  •  Fixed a bug where the system-defined user filter, when used in a custom gadget, displayed only users from the currently logged-in project in the Dashboard view.

  • Fixed a bug that triggered an "Invalid API key" error and eventually caused the integration to become inactive when creating a bug from QMetry to Azure. This issue affected existing QMetry-Azure integrations after configuring the Azure extension.

  • Fixed a bug that caused a connection error when adding the QMetry Custom Dashboard via an embedded URL in Confluence.

  • Fixed a bug that caused bulk export of test executions to get stuck in the "In Progress" state and eventually fail when exporting a test suite with a high volume of test cases.

  • Fixed a bug in the Audit Log for the Test Case module where update events for folders displayed incorrect metadata.

 

Build 8.21.0.1 - Release Date: 2025-07-10

Summary: Bug Fixes

  • Fixed a bug that caused the “Releases & Cycles” screen under Project Management to become unresponsive when expanding or adding a new release in projects with a large number of releases.

  • Fixed a bug that caused significant typing delays when editing test steps in test cases with multiple steps.

  • Fixed a bug where rich text content copied from other sources was displayed as HTML tags instead of formatted text in projects with the Rich Text Editor setting enabled.

 

Build 8.21.0 - Release Date: 2025-06-28

Summary: New Features, Improvements and Enhancements

 

New Features

Introducing QMetry Test Management Extension for Azure DevOps

The new QMetry Extension for Azure DevOps provides Azure users, including developers, business analysts, and product managers, with direct visibility into linked QMetry test cases and their execution results within the Azure Work Items synced as Requirements or Issues in QMetry. With QMetry test coverage visible within Azure DevOps work items, this extension ensures end-to-end traceability, enhances transparency and fosters stronger collaboration between QA and development teams.

The extension is essential for enabling integration between Azure DevOps and QMetry, allowing the mapping of a single QMetry project to multiple Azure DevOps projects.

Key Highlights:

  • Seamless Integration Between Azure DevOps and QMetry: Supports real-time synchronization of Azure Work Items into QMetry as Requirements and Issues. Enable users to view Azure Work Item details within QMetry and create or update Azure Work Items, synced as Issues, directly from QMetry.

  • No QMetry License Required: Azure DevOps users can view QMetry test cases and execution details within Azure work items without requiring a QMetry license.

  • Free for Enterprise Customers: Available at no additional cost on the Azure Marketplace for QMetry Test Management Enterprise customers using Azure DevOps.

  • Granular Admin Control: Azure Project Administrators have the flexibility to enable or restrict QMetry test visibility for all or selected work items within their projects.

  • Cloud Support Only: The extension supports integration with Azure DevOps Cloud services only.

Note: This update also applies to customers with existing Azure DevOps integrations. With the upgrade, configuring the extension is required to ensure continued functionality and seamless syncing between Azure DevOps and QMetry.

 

Test Case Creation Using Cucumber BDD Feature Files

Easily create test cases from Cucumber BDD feature files, reducing manual effort and aligning testing workflow with Agile and BDD methodologies. This feature is accessible from the following screens:

  • Requirement Details: Create test cases from the BDD section based on the feature file synced from the source code repository.

  • Test Case Module: Create test cases by importing feature files.

  • Test Case Details: Import individual scenarios directly into an existing test case.

Key Capabilities:

  • Seamless import of Scenarios, Scenario Outlines, Examples, and Rules from feature files.

  • Automatically converts tags into Labels and assigns them to the corresponding test cases.

  • Use test case key tags to update existing test cases or create new versions and requirement key tags to link test cases to requirements.

  • Imports initiated from the Requirement or Test Case modules run in the background. Users can monitor the import progress and view detailed logs for failures or warnings.

  • Examples from Scenario Outlines are automatically created as test case parameters and grids, improving parameterized testing capabilities.

 

Enhancement to Actual Execution Timer

  • The Actual Execution Timer now supports incremental time tracking, allowing accurate measurement of total time spent across multiple sessions. Consolidated time is displayed when the timer is restarted and stopped.

  • The running timer is now pinned at the top of the screen, displaying the relevant Test Case Key under execution. Clicking the link navigates users directly to the corresponding test case execution run.

  • The Timer and Actual Execution Time fields now support the HH: MM: SS format, providing greater precision and improved control over time tracking.

  • The recorded time is now preserved during user actions such as page refresh, screen navigation, back button clicks, or closing and reopening the tab/window, ensuring continuous time tracking and preventing unintended time loss. When paused, the timer will display the paused time in a distinct color to indicate its status.

  • Project admins configure the recording of the actual execution time only through the timer, preventing users from entering it manually to streamline the process. Additionally, the project administrators can set up the timer to automatically start when testers begin execution of any step in a test case. The new settings are available under the customization - execution status section.

 

Enhancements to Folder Management

  • Folder Description Support - Add descriptions to folders to communicate their purpose and scope, improving organization and team collaboration.

  • Folder Operations Consolidated Under Right-Click Menu - All key folder operations are now accessible via the right-click menu, enhancing usability and improving navigation efficiency.

 

Introduced Cascading Select List Support

  • Introduced a new user-defined field type: Cascading Select List, allowing configuration of single-level parent-child dropdown values to support more structured and dynamic value entry.

  • Enabled the support for syncing Cascading Select List fields from Jira work items into QMetry Requirements or Issues, ensuring consistent field mapping across systems.

  • Exploratory Testing Extension Upgrade - Users must upgrade their QMetry Exploratory Testing browser extension to the latest version to get support for cascading field enhancements and comply with QTM release 8.21. The latest versions of extensions are as follows: Chrome 1.2.7, Firefox 1.1.1, and Edge 1.0.7.

Note: Cascading Select List fields created in QMetry or synced from Jira work items are currently unavailable in QMetry Insights for custom reporting. Syncing these fields in QMetry Insights is planned for future releases.

 

Miscellaneous Improvements

  • The Project Description field has been enhanced from a 255-character string to a large text field, allowing teams to enter more detailed project information.

  • A Description field has been introduced for Releases, allowing teams to provide detailed information for each release.

  • The Estimated Time field in test cases, along with the Actual Attended Time and Actual Setup Time fields in test executions, now support input in HH: MM: SS format, offering greater precision and control over time tracking. Previously, only minutes were supported, limiting time-tracking precision. After the upgrade, the previous saved values, which were in minutes, will be changed to the new format of HH: MM: SS.

  • Improved the filtering and dropdown selection menus to expand and utilize the available space when selecting filter options.

  • Enhanced Field Length Support

  • Project Name, Release Name, Cycle Name, and Build Name now support up to 128 characters. Platform Name now supports up to 255 characters.

  • Custom Field Name and List Name now support up to 50 characters. List values now support up to 255 characters.

 

Performance Improvements

  • Improved performance when displaying Azure-synced issues on the Issue List and Link Issues screens.

Security Enhancements

  • Addressed multiple security vulnerabilities identified through routine internal audits and penetration testing to enhance overall application security and ensure compliance.

 

Jira Integration Add-on Upgrade

  • Release v8.21 requires installation/upgrade of the QMetry Integration for Jira app to v2.3.3 for organizations using Jira 10 and v2.3.3_jira9 for organizations using Jira 9 or below. For customers utilizing Jira Cloud, the add-on will upgrade automatically.

 

Deprecation Notice: Rally Integration

With the release of QMetry v8.21, integration with Rally is officially deprecated. The following changes apply:

  • New Rally integrations are no longer supported.

  • Syncing Rally work items as requirements and issues is no longer supported.

  • All existing Rally integrations are disabled, and related features are no longer available.

  • This change applies to both QMetry SaaS and On-Premise deployments:

  • For SaaS, Rally integration is discontinued from version 8.21 onward.

  • For On-Premises, customers on version 8.20 or earlier can continue to use the integration until they upgrade to v8.21.

 

Bug Fixes

  • Fixed a bug that intermittently exported dashboards in PDF format as blank.

  • Fixed a bug that caused certain Jira work items to fail to sync to QMetry due to special characters in a custom field of type Labels.

  • Fixed a bug that prevented SAML authenticated users from enabling the Flaky Score AI feature at the project level.

  • Fixed a bug where Jira Issues remained visible in the source QMetry project even after being moved to a different Jira project.

  • Fixed a bug that prevented certain users from navigating to the Execution screen or performing actions like approving or closing an execution due to missing default execution column view.

  • Fixed a bug that prevented users from deleting test cases linked to multiple test suites containing a higher count of test case executions.

  • Fixed a bug that prevents users from logging into QMetry using the 'Login with SAML' option with the Org Code generated in lowercase.

  • Fixed a bug that prevented the bulk moving of multiple test suite folders within a project.

  • Fixed a bug that caused the System Reports sub-menu to appear misaligned in collapsed mode, and the browser zoom was set below 100%.

  • Fixed a bug that prevented cloning the sample 'Health Tracker' project included with QMetry Cloud evaluation instances.

  • Fixed a bug that caused duplicate entries for the integrated Jira instance when a different Jira instance database was cloned or restored.

  • Fixed a bug where data in large text fields was not auto saved when clicking outside the textbox, requiring users to click Save.

 

Build 8.20.0.3 - Release Date: 2025-06-02

Summary: Bug Fixes

  • Fixed a bug that prompted SAML users for re-authentication despite an active SSO session.

  • Fixed a bug that prompted SAML users for re-authentication despite not having reached the configured idle session timeout limit.

  • Fixed a bug that did not retain the saved changes when updating a user's role to "No access" under the Customization > Users, role mapping section.

 

Build 8.20.0.2 - Release Date: 2025-04-25

Summary: Bug Fixes

  • Fixed a bug that prevented users from deleting test cases linked to multiple test suites having a large number of test executions.

  • Fixed a bug that prevented certain SAML users from generating test cases using QMetry Intelligence.

 

Build 8.20.0.1 - Release Date: 2025-04-21

Summary: Bug Fixes

  • Fixed a bug that prevented users with the necessary permissions from copying and moving test cases from the test case module list view.

  • Fixed a bug that prevented syncing updates for some users from Okta to QMetry via the Aquera app when SCIM was enabled.

  • Fixed a bug that prevented the creation and execution of advanced query reports using Common Table Expressions (CTEs) in the query editor.

  • Fixed a bug that prevented the deletion of a custom role, which appeared unassigned to any user but was still internally linked to users converted from regular to read-only access type and were previously assigned that role.

  • Fixed a bug where copying a test suite from within a folder incorrectly created the copy in the project root folder instead of the default destination path.

  • Fixed a bug that prevented updating the description for tabular gadgets added to dashboards. 

Deprecation Notice: Rally Integration

As part of our commitment to delivering high-value features in QMetry, and based on current usage insights, Rally integration will be deprecated in the upcoming QMetry v8.21 release, scheduled for June 2025. The following changes will take effect:

  • The integration of Rally projects to sync work items as requirements and issues will discontinue. New Rally integrations will no longer be allowed. Existing Rally integrations will be disabled, and all related features will no longer be accessible.

  • This change will affect both QMetry SaaS and On-Premises customers. The Rally Integration features for SaaS environments will be discontinued with the release of version 8.21. On premise customers using QMetry version 8.20 (expected release in May) or earlier can continue to use the integration until they upgrade to version 8.21.

If your organization is impacted or is still using/planning to use the Rally integration, please create a support ticket with QMetry Support for further assistance

 

Build 8.20.0 - Release Date: 2025-03-29

Summary: New Features, Improvements and Enhancements

 

New Features

Enhanced Folder Selection

Users can now browse and select a folder directly on the creation screen when creating Requirements, Test Cases, and Test Suites. The folder path is now visible on the details screen, eliminating the need to hover over the folder breadcrumbs. Users can also move test assets between folders by updating the folder path directly on the details screen.

Key Improvements

  • Folder Selection for Cross-Functional Module Test Assets

    • This enhancement improves folder selection, particularly when creating test assets from cross-functional modules for the following operations. Previously, these operations autosaved such assets to the project's root folder, requiring manual relocation.

      • Creating a Test Case from a Requirement or an Exploratory Testing (ET) session.

      • Creating a Test Suite from a Requirement, Test Case, Requirement Folder, Test Case Folder or an Exploratory Testing (ET) session.

      • Creating a Requirement from an Issue.

  • Folder Selection for Auto-Generated Test Cases

    • Select the desired Test Case folder from the Details tab when auto-generating Test Cases using QMetry Intelligence (QI) from the Requirement and Test Case modules.

  • Folder Selection for Automation API Integration

    • Specify the Test Case folder path parameter to automatically organize newly created Test Cases into the desired folder when uploading automation results using the Automation API.

 

Improved Folder Navigation and Sharing

Users can now enjoy enhanced navigation and collaboration features with folders.

  • Clickable Folder Path: The folder path breadcrumb displayed at the top of the Requirement, Test Case, Test Suite, and Test Execution detail screen is now clickable. Each folder in the breadcrumb is interactive, enabling users to seamlessly navigate to the test asset list of the selected folder.

  • Folder Link Sharing: Users can easily copy a direct link to a folder by right-clicking on it or from the folder path breadcrumbs. Sharing this link allows others to directly access the specified folder within the folder tree structure, improving collaboration.

 

Enhancements to Auto Generation of Test Cases

Auto Test Case Generation (ATG) using QI is now Generally Available

  • The Auto Test Case Generation (ATG) AI feature has officially transitioned from Beta to General Availability (GA)!

    • ATG is an AI-powered feature designed to:

      • Generate test cases automatically based on requirements and user-provided descriptions.

      • Enhance existing test cases and steps to improve their quality and completeness.

    • Benefits:

      • Boost productivity by reducing the time and effort required to create comprehensive test cases.

      • Ensure thorough test coverage by generating test cases that effectively cover various scenarios.

Auto-Generate a Test Case Using an Existing Test Case as a Reference

QMetry Intelligence (QI) now allows testers to create or enhance test cases by leveraging any existing test case as a reference and applying user-provided instructions. QI generates test case and step details while retaining relevant information from the referenced test case, ensuring better test coverage and alignment with user-specified changes. This feature supports three key workflows:

  • Create a New Test Case - Generate a new test case using an existing one as a reference, incorporating the modifications specified by the tester.

  • Enhance an Existing Test Case - Use an existing test case from the project repository as a reference to update another existing test case by applying user instructions to modify its description and test scenarios while retaining relevant steps.

  • Improve Test Steps - Enhance existing test steps based on user-specified changes to ensure alignment with evolving testing objectives.

 

Enhancements to Test Steps View and Edit Experience

  • Persistent Step Number and Attachment Columns: The Step Number column is now locked and always visible, even when scrolling horizontally. This feature helps users accurately track the row they are editing, which minimizes errors and enhances efficiency. Additionally, the Step Attachment column is now permanently positioned next to the Step Number column, allowing quicker and easier access to view and edit attachments.

  • Improved Step Action Option Accessibility: The step edit and action gear buttons for inserting, deleting, duplicating, moving, or copying steps are now accessible at the right end of each step without requiring horizontal scrolling when multiple columns are present. The gear button appears upon hovering over the right end of the step row, enhancing usability and streamlining the editing process.

  • Full-Screen Step Editing: A new option to expand steps to full-screen is now available when editing test case steps. This feature allows users to maximize the step editor, using the entire screen for better visibility and an improved editing experience.

  • One-Click Column Name Expansion: The Step Table now has a new Expand Column button that allows users to view the full names of all field columns with a single click, eliminating the need for manual column expansion.

 Security Enhancements

  • With release v8.20.0, the Tomcat version on the QMetry SaaS infrastructure has been upgraded to v10.1.39 to mitigate the Tomcat security vulnerability CVE-2025-24813.

Miscellaneous Enhancements

  • Users can now adjust column sizes to improve readability and usability across the following screens. Additionally, the newly introduced “Restore Width” option enables resetting columns to their default size.

    • Test Suite Screen: Linked Test Cases section on Creation and View Details screens.

    • Test Case Screen: Linked Requirements, Test Executions, and Issues sections.

    • Requirement Screen: Sections for Linked Test Cases and Issues.

    • Issue Screen: Sections for Linked Execution Runs and Requirements.

 

Bug Fixes

  • Fixed a bug that allowed test cases to be successfully imported via an Excel file without triggering a validation error, even when a mandatory field was left empty in the imported file.

  • Fixed a bug where the Status, Activity, and Module filters on the Scheduled Tasks screen displayed duplicate values.

  • Fixed a bug that prevented the auto-population of the test case and step details in the issue summary and description when creating an issue from the execution screen for test cases containing more than 50 steps.

  • Fixed a bug that prevented testers from executing test cases on the execution screen when accessing the test execution via a URL copied using the "Copy Link" feature.

  • Fixed a bug that prevented date-type custom fields from displaying on the detail screen when the section contained multiple date field.

  • Fixed a bug that prevented displaying custom fields with names containing the “Approval” keyword on the detail screen.

  • Fixed a bug that allowed users without the “customization” modify permissions in the target project to create custom fields when copying or moving test cases across projects.

  • Fixed a bug that prevented test step custom fields from being displayed on the execution screen for shareable test cases copied to another project.

  • Fixed a bug that prevented users from executing a copied test suite, even after linking it to a release and cycle, if the original test suite had no associated release or cycle.

  • Fixed a bug that displayed an incorrect count of associated projects for a custom field on the Manage Fields screen.

  • Fixed a bug where test cases did not appear in the Link Test Case section when filtered by folder while linking to a test suite. The issue occurred when renaming projects having over 1000 test case folders.

  • Fixed a bug that prevented test cases from appearing in the “Audit Log” report when a filter on “Approved Test Cases” was applied.

  • Fixed a bug that prevented SAML-authenticated users from downloading attachments linked to assets from the attachments tab of test assets.

  • Fixed a bug that prevented the complete Platform list from being displayed when creating a new test suite from the Requirements or Test Case from a new tab.

  • Fixed the download and open attachment icons across all modules to clearly distinguish between downloadable and URL-based (non-downloadable) attachments.

  • Fixed a bug that caused the Auto-Organize Requirements in Folders feature to stop syncing after mapping a new Jira issue type to the QMetry Requirements module.

  • Fixed a bug in Jira-integrated projects where the “linkedRqCount” column in the “issue” table within the Advanced Query Reports schema displayed an incorrect count.

  • Fixed a bug that allowed users without link permissions in the source project to link its test cases to a test suite in another project where they had link access. With this release, users must have the necessary link access in the source and destination projects to link test assets across projects.

  • Fixed a bug that prevented specific system gadgets, such as Planned vs Actual Executions and Test Suite Execution Summary, from retrieving and displaying relevant records when added to a custom dashboard due to folder filters not being auto-applied correctly.

 

Build 8.19.1 - Release Date: 2025-02-08

Improvements & Enhancements

 

Attachment Enhancements

  • Rich text fields now support adding inline images of up to 100 MBs.

  • A "Select from Linked Attachments" option has been added to the rich text editor under the Insert Image tool, enabling users to embed images directly from the attachments section of the test entity. Deleting the original image from the attachment section will make the embedded image unavailable.

  • A "Copy Link" option has been added for all files in the attachments section, allowing users to copy the URL of an image or file. This URL is intended solely for referencing files or images within the application's rich text editor. Deleting the original image or file from the attachment section will make its reference inaccessible.

  • Accessing non-image files added as attachments using URLs outside the QMetry application will require QMetry authentication for added security, except from within the integrated Jira.

Performance Improvements

  • Improved performance for loading issues synced from the Jira on the Issue List and Link Issues screens across the application.

Jira Integration Add-on Upgrade

  • Release v8.19.1 requires installation/upgrade of the QMetry-Jira Integration app to v2.3.2 for organizations using Jira 10 and v2.3.2_jira9 for organizations using Jira 9 or below. For customers utilizing Jira Cloud, the add-on will upgrade automatically.

Bug Fixes

  • Fixed a bug where cloned projects integrated with Jira failed to display newly added Jira custom fields or sync data updates after the original project was archived.

  • Fixed a bug where renaming a project with a large amount of data did not correctly change the root folder name for each module. This issue caused test cases to disappear from their folders, making them unsearchable when filtering by folder in the test suite and unavailable for linking.

 

Build 8.19.0.1 - Release Date: 2025-01-20

Summary: Bug Fixes

  • Fixed a bug that prevented assigning project access to read-only users and caused an exception.

  • Fixed a bug that prevented assigning project access to users created as read-only while converting them to regular users.

 

Build 8.19.0 - Release Date: 2025-01-04

Summary: Improvements & Bug Fixes

 

Permission Enhancements

  • 'Release and Cycle' permissions have been introduced to control the creation, modification, archiving, and deletion of releases and cycles within a project. These permissions are now separate from the 'Modify' project permissions, offering more granular control over their management.