Release Notes 8.10.x

Fixed a bug that prevented copying data with tables and hyperlinks into comments and the actual outcome field on the execution screen.

Fixed a bug that prevented access to the issue module for some projects due to duplicate epic links.

Fixed a bug that prevented seamless syncing between Jira stories and QMetry requirements for some projects due to the duplication of some synced issues.

Fixed a bug that delayed syncing updates from Jira/Azure to QMetry..

Fixed a bug that gave an error while cloning projects that contain a large number of test executions.

Fixed a bug that did not fetch all test cases created through Automation API (apiVersion=1) when filtered by "Testing Type".

Fixed a bug that prevented users having the default QA Manager role from creating a defect into Azure.

Fixed a bug that did not preserve HTML formatting of Jira descriptions synced to QMetry.

Fixed a bug that prevented an appropriate error from being displayed when creating issues with descriptions longer than 65553 characters.

`QMetryJira Integration` app v2.2.0 is released compatible with Jira Software v9.0 and v9.1. Customers hosted on the Jira server/data center will need to update the app manually.

QMetry v8.10.3 upgrades all third-party libraries used internally to their latest version making QMetry more secure by removing any existing vulnerabilities.

Improved UI experience - QMetry web application upgraded with a new version of Angular framework 13.

A compatible version of Automation Agent 8.10.3 is available with this QMetry upgrade to v8.10.3. The latest agent supports only Open JDK 17.0.2. Users should upgrade the JDK & Automation Agent post-upgrade.

Fixed a bug that displayed list values from the current project instead of the selected project after sorting list values while editing the user-defined fields.

Fixed a bug that prevented unlinking platform from a test suite associated with too many platforms and test cases.

Fixed a bug that prevented some users from accessing test case folders within a cloned project.

Fixed a bug that prevented searching users in the user list while sharing custom report gadgets and dashboards.

Introduced multilevel closure workflow for test execution runs.

The closers' user list has been separated from the approvers' list to facilitate the change with this release. The closure workflow will have a new level containing users copied from the final approval workflow level.

Added a bulk operation to request a change on test run executions having closures initiated to allow changes before final closure.

Fixed bug that prevented users from generating the Part 11 authentication token unless provided create/update user permissions.

SAML users can now authenticate assets for Part 11 enabled projects using an authentication token.

QMetry and LDAP users can now alternatively authenticate test assets for Part 11 enabled projects using an authentication token with settings enabled by the super admin.

Administrators can set up to 30 reviewers and approvers at all levels for an eSignature enabled project.

For the QAF framework, the attachments associated with sub checkpoints are uploaded to their respective test case steps when uploading automation results.

For QMetry projects using the internal issue module, the "Error message" and "Trace" for the automated test executions get added as a text attachment to the bug for developer reference.

Skip status in the automation result file will be applied as "Not Applicable" instead of "Not Run" for automation test executions upload.

QMetry Test Management plugins for Jenkins, Bamboo and Maven show test suite details and import status in the console outputs for reference. A newer version of the following apps compatible with this change is released.

The total execution count for the test case gets displayed under the 'Test Case' panel in Jira.

Release 8.10.1 upgrade requires an install/upgrade of the latest version v2.1.9 of the QMetry Jira Integration app. This version is compatible with Jira software v8.22. For customers using Jira Cloud, the add-on will be auto-upgraded.

Improved UI experience - web application upgraded with Angular framework version 13.

Fixed bug that reset the current folder selection to the root folder post performing bulk operations or moving/copying assets.

Fixed bug that prevented displaying test cases for bulk operations when moved/copied to an eSignature enabled project.

Fixed bug that prevented displaying attachments and bugs on closed test executions for an eSignature enabled project.

Fixed bug that caused QQBot duplicate predictions to stop working while authoring test case steps.

Fixed message tip on execution screen to guide testers to map missing parameter values for parameterized test cases.

Fixed bug that prevented importing automation result file of Robot framework that did not contain test case steps.

Optimized processing of Jira, Azure, and Rally integration webhooks when too many webhook requests are received in a short time duration.

Fixed bug that intermittently displayed an error and prevented some gadgets from loading when users logged in for the first time during the day and accessed their custom dashboards.

Fixed a bug that linked the latest version of the test case instead of reusing an already linked version on the test suite while uploading results using Automation API with the is_matching_required parameter as false.

Fixed a bug that auto-linked requirements mentioned in the automation results to an incorrect test case version while uploading results using Automation API with the is_matching_required parameter as false.

Improved performance for automation test results import using Automation API, QMetry Test Management Plugin for Jenkins, QMetry Test Management Plugin for Maven and QMetry Bamboo Integration app.

The automation result import process now reuses the existing test case version for which summary and steps match exactly when the test case has multiple versions.

Introduced a new parameter "is_matching_required" that allows updating execution status on a linked test case version or latest version by matching test case keys in the result file instead of creating a new version even if the test summary and steps do not match.

New test suites can be created in a specified folder while importing automated test results using the "tsFolderPath" parameter.

The job status and the test suite details of the automation test result imports are now visible in the scheduled tasks section.

The "test suite key" parameter will no longer be available directly in the automation API response. The automation API response will now provide a "request-id" parameter. A follow-up API using the "request-id" parameter will return the test suite key and import status. For more details, refer to the API changes section.

Added support to import the test case description for the cucumber framework.

Added support for importing test case step attachments for the QAF framework.

Reuse of existing test cases is supported using entity key for Junit framework.

A newer version of the following apps compatible with the above changes of v8.10 is released.

The value of the estimated time field on the test case detail screen now accepts up to 99999 minutes.

Added option to select/unselect all fields on the arrange column menu in the list grids.

Release 8.10 upgrade requires to install/upgrade the latest version v2.1.8 of Jira Integration - QMetry Enterprise App in Jira. For customers using Jira Cloud, the add-on will be auto-upgraded.

Fixed bug that changed the execution type of manual test execution to automated on the execution screen after manual sync of the latest test case version.

Fixed bug that prevented navigating backwards on test case steps using shift-tab keys.

Fixed bug that allowed updating a sharable test case on the same version for an eSignature enabled project.

Fixed bug that did not show the screenshots in the comments section of issues synced from Jira.

Fixed bug that made the QMetry server inaccessible due to high memory utilization triggered by the large number of Jira webhooks received in a short duration.

Fixed a bug that prevented the upload of attachments with file extensions .7z, .log, .py (python) and .ps1 (PowerShell).