Release Notes 8.21.x

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.

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.

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.

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.

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.

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.

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 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.

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.

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

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

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.

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:

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.