Release Notes 8.11.x

Build 8.11.2 - Release Date: 2022-11-15

Improvements

  • Updates to Spark v3.3.1 and JDK v17 in QMetry Insights fix a potential data sync failure caused by a bug in the older spark version.

Build 8.11.1 - Release Date: 2022-11-04

Bug Fixes

  • Fixed a bug that prevented the loading of test cases in Jira's QMetry test case panel if the test executions were large in number.

  • Fixed a bug that prevented displaying user-defined fields in visual reports.

  • Fixed a bug that exported test case steps executions in excel or CSV showing an incorrect count of defects linked.

  • Fixed a bug that prevented syncing Jira stories to the Requirement module for a project integrated with multiple Jira projects by a user that got deactivated later.

  • Fixed a bug that displayed an error requiring incorrect build permission while loading the issues and the combined view tab for a requirement.

Build 8.11.0 - Release Date: 2022-10-15

Improvements, Enhancements and Bug Fixes

Improvements and Enhancements

Reporting and Dashboard

  • Introduced Planned vs Actual Execution analysis gadget under the Test Execution Summary report to help QA managers understand the current and expected execution rate to meet the release timelines.

  • Export complete test execution details in a PDF as audit and compliance evidence. Organizations that have subscribed to the Integration app will get an option to export execution details in a pdf.

  • Dashboard gadgets will always display the counts or percentages without a need to hover.

  • Dashboard gadgets will preserve the user's preferred graphical or chart data report view. Shared dashboards and PDF export will display the gadget's view according to the owner's preference.

Issue Module

  • Attach images/files while creating defects under projects using the internal issue module.

  • Add multiple attachments while creating a defect in the integrated external trackers (e.g. Jira, Azure or Rally) from within QMetry.

Change Log

  • The change log highlights the difference between old and updated values to make it easier for users to understand the updates.

  • Change logs record detailed step-level updates when creating a new version of the test case.

eSignature

  • Introduced email notification settings for eSignature-enabled projects to allow project administrators to enable or disable forced notifications on events like review, approval, closure, or a request change.

  • Administrators can add up to 50 reviewers and approvers at all levels for an eSignature-enabled project.

  • The email notifications on review, approval, closure and request change will contain the asset summary along entity key for easy identification.

Automation (Only for SaaS)

  • Achieve traceability by auto-linking internal requirements with Junit test cases uploaded through automation import using the keyword "requirementEntityKey" to specify the entity key in the result file.

  • Achieve traceability by auto-linking requirements synced from external trackers (e.g. Jira, Azure, Rally) with Junit test cases uploaded through automation import using the keyword "requirementExternalKey" to specify the external issue/work item key in the result file.

Miscellaneous Improvements

  • Sync the latest version of the requirement to its linked test cases individually or in bulk using the new "Sync Latest Version of Requirement" option on the requirement screen > test cases tab.

  • Sync the latest version of the test case to its linked requirements individually or in bulk using the new "Sync Latest Version of Test Case" option on the test case screen > requirements tab.

  • Release 8.11 upgrade requires an install/upgrade of the QMetry Jira Integration app latest v2.2.1. For customers using Jira Cloud, the add-on will be auto upgraded.

Bug Fixes

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

Publication date: