Release Notes 8.5.x

Introduced Issue Module for projects synced with Jira. This will allow testers to view/update Jira issues directly from QMetry (except workflow status).

QMetry now saves user Jira credentials and uses them for authenticating updates made to Jira issues. Users can modify/revoke their saved Jira credentials from Jira Integration page.

Introduced "Part 11 Compliance Authentication" for E-signature enabled projects. This option would enable mandatory authentication for test case approval, test suite run status change to in-progress/closed and test case execution status change.

Sync Jira Epics as requirements with support for limited fields.

Track test case executions as "Manual" or "Automated" by setting the new "Execution Type" field on execution screen.

Ability to search assets in filters by using comma separated entity IDs.

Test execution screen now allows testers to resize test case columns to view complete details.

Export test assets with only required field that are visible on the list grid; instead of all the fields.

Issue System Reports - Issue Summary, Issue Open vs Closed - Cumulative & Issue Trend Over Time will now display issues synced for Jira integrated projects.

Improvements to Bulk Execute screen.

QMetry Application is now supported on Safari Browser.

QMetry Installation is now compatible with Open JDK 11 & Apache Tomcat 9.x.

Jira Integration support for versions 8.7, 8.6 and 8.5

Performance Improvements

Fixed a bug that prevented syncing requirements in some JIRA integrated projects.

Fixed a bug that failed to search some issues using global search.

Fixed a bug that caused elongated hyphens to be replaced with black space when a test case is exported in excel.

Fixed a bug that did not allowed selecting all records across pages while generating the traceability report.

Fixed a bug that displayed duplicate issue statuses in the search list for a Jira integrated project.

Fixed a bug that displayed issue workflow statuses in the search list that are not part of the integrated JIRA Project.

Fixed a bug that prevented fields from getting auto mapped while importing test assets.

Fixed a bug that allowed exporting all the assets instead only the filtered assets.

Fixed a bug that prevented integration with GitHub organization account.

Fixed a bug that prevented filter to be preserved for Test case Status on link test case to testsuite search.

Fixed a bug that imported Jira issues to QMetry with the created by user who integrates the Jira project with QMetry project instead of the user with whom the add-on is integrated.

Release 8.5.6 upgrade requires to install/upgrade the latest version v2.0.3 of Jira Integration - QMetry Enterprise App in Jira.

Post upgrade mandatory sync of Jira integrated projects is needed to display all the mapped Jira fields in the new Issue module.

Fixed a bug while importing using result import API that caused test case and test suite fields to be blank even though settings for auto-create values are enabled or when the fields are marked mandatory.

Right-click on entity key to open assets in new tab.

Show/Hide system field - Testing Type

Set Test suite and Test case fields while importing automation results using Automation API, Jenkins & Bamboo plugins (Refer APIs Changed Section - Automation API)

Support for Bit Bucket & Git server version for BDD integration.

Branch support for Bit Bucket & Git integration for BDD.

Link test cases to test suites of other projects without switching the project

Create/update and activate/deactivate rights can now be assigned separately while assigning user modify permission

Make reporter selection mandatory/optional for creating bug from QMetry to Jira

Open APIs for BDD Integration. (Refer APIs Added)

Fixed an issue, that prevented a user to edit custom lists, in spite of having project and customization modify rights.

Fixed an issue, that prevented users from generating Open API key in spite of having view rights of the integration module.

Fixed an issue, that prevented other users from generating Exploratory Testing API key if an exploratory testing session for any user is in progress.

Fixed a bug that showed a warning for insufficient rights to users while opening a test case, if their role did not have view user settings permissions.

Fixed a bug that prevented the users to rearrange tabs within test cases, if their role did not have view user settings permissions.

QMetry Menu is now classified as per the QMetry Apps to easily differentiate respective app features.

Project admins now have an option to disable auto addition of list values while importing from excel that will prevent users from importing values that are not part of list.

Deleted requirements and issues synced with Jira will now be auto deleted from QMetry as well.

Enhanced requirement filters to allow search based on Jira fields.

Redesigned test asset detail view; now has organizable tabs as per different sections; allowing one click access to users.

Admin can configure a custom email address within email notification template that will direct users to get support as per the defined organization process. (Only for server edition)

System fields can now be made mandatory or optional.

Platform attribute details are now available in test execution section of testcase & test suite

Approval status of test cases in eSignature enabled projects is now available in the export

Included HTML/XML editor support in large text fields for text formatting.

Shareable test case details like key, version and steps are now displayed in the testcases using them.

Shareable test case steps are now shown under QMetry test cases section in Jira.

QMetry requirement key is now shown in Jira issue synced with QMetry, clicking on the key opens requirement in QMetry.

BDD integration now supports QAS framework feature files.

Revamped QMetry panel in Jira now has separate sections for synced requirement, linked test cases & BDD details.

Auto exception reporting to QMetry - For Server Customers.

Fixed bug that allowed using archived values when imported using excel.

Fixed bug that caused slowness when editing testcase with large number of steps.

Fixed bug that renamed dashboard when generated for multiple projects.

Fixed bug that prevented creating an issue in Jira, if field or values have special characters like comma, quotes or colon.

Fixed bug that did not validate certain valid email addresses while creating new users.

Added support for SMTP integration that does not require user name and password for authentication.

Import TestNG Results by mapping Test "Name" as Test Case Summary and Test Method "Name" as Test Step.

Test Category and Priority system list values can be archived.

Fixed bug that prevented admins from editing user details if SMTP is not configured.

Fixed bug that did not allow to un associate Jira custom fields from QMetry modules that were mapped before Release 8.5

Testcase estimated time is now available while generating custom reports using Visual Analysis.

Pending Test cases report in My Dashboard displays test cases which are not executed (Not Run status) and assigned to selected user.

Executed Test cases report in My Dashboard displays test cases which are executed by selected user.

QMetry - Jira Integration add-on is renamed to “Jira Integration - QMetry Enterprise” in Atlassian Marketplace.

Jira integration changes to comply with Atlassian GDPR privacy policy

Improved overall performance and scalability using Redis caching

Fixed bug that caused error while opening a requirement imported from Jira containing double quotes.

Fixed bug that prevented import of results using Automation API if Test suite has mandatory fields with default values.

Fixed bug that prevented bulk linking requirements to testcases that had requirements already linked.

Fixed bug that did not allow scheduling of reports in Chrome.

Fixed bug that gives error while import of results using Automation API if Test suite has mandatory fields with default values.

Fixed bug that display permission error when creating an internal issue.

Fixed bug that did not allow to set assignee while creating issues during exploratory testing; released chrome add-on version 1.0.2

Easily filter test cases that are not planned for execution for a combination of Release and Cycle

Hide test cases already linked to a test suite to avoid duplicate linkage of test cases

Latest search filters will be preserved on link test case to test suite screen

Bulk sync testcases to their latest version on the execution screen

Reuse test cases based on test case key for TestNG framework.

Configure hierarchy of Test suite, Test case or Test case step while importing automation results for TestNG and JUnit.

Test suite execution summary report displays total number of platforms and test cases linked to a test suite.

Resolved issue verification report displays linkage hierarchy for issue linked at test case or test case step.

Visual Analytics – added column for reporter & created by for issues imported from Jira.

Test case description shall be auto added to Issue description when creating an Issue from the execution screen.

Choose folder while importing requirements from Jira.

Integration support for Jira version 8.x.

Quick button to copy API key.

Test category is sorted alphabetically for easy assignment.

Sorting of Test assets will be preserved on all modules grids.

Shared test case will have details of test cases that are using it.

Improved performance while editing test steps when a test case has a large number of steps.

Updates made to test case steps are preserved while creating a new version from the detail screen.

Get list of Testcases linked to a Shared Testcase.

Auto fill parameter values in data grid

Integrate multiple Jira Projects with a single QMetry Project. (More...)

QMetry-Jira integration requires mandatory installation of QMetry Integration add-on in Jira. Jira integration no more requires authentication with Jira admin credentials. (More...)

Be on top of the discussions happening on the Jira story as QMetry requirements syncs latest 10 comments made on the story.

Simplified mapping of Jira custom fields with QMetry Requirements & Issues.

Sync Jira Labels & Sprints in QMetry for imported Requirements and Issues.

New Report - Test Suite Summary report summarizes the count of testcases executed and their execution status for a selected release and cycle.

New Report - Online Logged in User report displays the list of users logged in to QMetry and their last activity time.

Top Issue Report, Traceability Report by Issue, Execution - Issue Summary Reports & Test cases with Issues Report now shows bugs linked at Test Case Step.

Custom Reports are now editable.

Approval Workflow Report now shows "Approved Date" for Testcases and Test Executions.

Audit Log Report now shows Data Parameters and Data Grid modifications.

Change Log Report now displays the name of the field which was edited with it's type and key.

Generate custom reports separately for Requirements/Issues created in QMetry and imported from Jira.

Organize Testcase and Testcase Step columns on execution screen.

Enable Testcase custom fields on Test execution screen. (Large Text fields are excluded).

View Estimated and Remaining execution time at Test suite view and Platform view.

Add/manage builds directly from Test execution screen.

Archive Test suites before they are deleted.

Import attachments for test executions via automation API for Cucumber and QAF frameworks.

Link Requirements, Testcases, Test suites & Issues filtering them by custom fields.

Archive folders across QMetry. Archiving folders will archive & hide all subfolders and assets under it.

Testcase Summary and Entity Key are shown on the detail page of testcase link screen in Jira.

Bulk link Releases/Cycles/Testcases to Requirements imported from Jira.

Hide/unhide multi look up fields as columns on list grids for all modules.

Global Project Search gets data for sharable testcases.

Requirement module would have BDD section visible only when a version control system is configured for the project.

Archived Releases & Cycles will be hidden from lists across all modules.

Multiple users could be notified while pushing BDD modifications to VCS.

QMetry Internal Issue module will not be enabled for projects that have Jira integrated.

Issue can be created from QMetry to Jira but have to edited in Jira.

Requirements imported from Jira cannot be filtered based on Jira fields in the List grid & Bulk Operations.

Issues cannot be linked/filtered to Requirements/Test Executions filtered based on custom fields.

QMetry Test case links created in the Jira Issue link section. (Not needed any more as Testcase links are visible in Test Case Section in Issue)

Import of Jira Requirements & Issues via user defined JQL. (Not needed any more as Jira QMetry Project mapping requires mapping of Issue Types for Modules.)

Following Issue Module Reports will not display data for QMetry Projects that are synced with Jira Project, as these reports can be viewed directly in Jira.