Version 6

Jira Administrators can now select all the executions in the Search Test Executions page to archive.

Zephyr Squad introduces new option to limit the issues imports on Importer. You can find this option on the Zephyr Squad General Configuration page.

For easier and faster navigation, the Search Test Executions page will now open on the last selected search type page: Basic or Advanced.

For the sake of a clearer UI, Zephyr Squad introduces new options to hide or show the Help menu item and Test Automation menu. You can find these options on the Zephyr Squad General Configuration page.

The Zephyr Squad API worked on project pages for which the app was disabled.

On the Cycle Summary page, resizing the test cycle and folder column did not work correctly.

Users were unable to switch the editing mode from wiki-markup to text in the test step editor.

The Search Test Executions grid didn't reflect assignments of test executions made via Zephyr Squad API.

GitHub integration issues: some changes in GitHub repositories didn't cause changes in Jira issue statuses.

This release updates the Log4j library to version 2.16.0 to address the CVE-2021-44228 (Log4Shell) and CVE-2021-45046 vulnerabilities.

If you use Test Automation and have ZBots configured, be sure to also download the updated ZBot software to fully mitigate the vulnerability risk.

Test cycle information returned by the Zephyr Squad Server API includes the createdByDisplay and modifiedByDisplay fields. They contain the display names of the users specified by the createdBy and modifiedBy fields.

Jira Advanced Roadmaps pages failed to load if the Zephyr Squad Server license had expired.

When exporting test executions to an Excel file, test step data could end up in wrong columns.

The Search Test Executions page now has the Select all executions check box. You can use it to select all executions found by your query:

You can export test executions with attachments by using the new HTML (with attachments) export mode on the Search Test Executions page:

When adding tests to a test cycle or folder, you now have an option to create a new cycle or folder.

You can now use JQL queries to find tests to be added to a cycle. To do that, use the new Via JQL Search tab in the Add Tests to Cycle and Add Tests to Folder dialogs:

The Close button was missing in the Execution history dialog.

Test Automation tasks were not displayed after a Zephyr Squad update.

Test execution data exported to a CSV or Excel file had extra HTML tags in custom field values.

Linking a defect on the test execution screen or updating a test execution status generated multiple entries in the execution history.

The import of test cases from an Excel file could get stuck in instances with the Automation for Jira app.

The Create Zephyr Test command in the issue view sometimes did not link the created test to the issue. This happened if all issue link types in Jira settings had been deleted.

The performance of Test View agile boards has been improved to handle a large number of active sprints and tests more efficiently.

The help menu now contains links to the Zephyr Squad documentation and Community:

The Labels filter in the basic search mode on the Search Test Executions page did not show existing labels.

Zephyr Squad Server can now automatically create defects for failed test executions. For more information, see Defect Configuration.

The new columns on the Cycle Summary page show Execution comment and Description of test executions, and the new column on the Issue View page shows Execution comment of test executions.

Now, you can use the predefined filter on the Search Test Executions page to view details of archived executions.

Zephyr showed an error when the date format was changed.

Test cases could not be imported if all issue link types were removed from the Issue linking configuration.

Tests created from an issue with the Backlog status did not link to the parent issue automatically.

The Test Details wiki markup did not save the input data.

The Zephyr Custom fields with an empty value could not be displayed in the custom field selector.

The image uploaded to the description issue field was displayed incorrectly.

The ZQL query did not display any results when the Logged Time or Estimated Time fields were used on the Search Test Automation page.

Test Automation could not be assigned to a user if unassigned issues are not allowed in Jira General Configuration.

The Test Issue Importer did not import Excel files if the security field was set as required in the Issue Security Scheme.

Enhanced the tracking of migrated objects during the JCMA migration.

Requirement to defect Traceability did not work when it was filtered on a specific version.

You can now archive test executions. This hides them from the dashboards and search but preserves their data in case you may need it later.

All archived test executions are displayed in Tests > Search Test Executions > Archived Executions. You can also restore (unarchive) test executions at any time.

For more information, see Archiving Test Executions.

REST API also has new operations to archive test executions and work with archived executions. See Test Executions API for details.

Test folders could not be deleted.

Archived Jira issues still had the Create Zephyr Test button.

The list of versions in the Clone Cycle dialog included archived versions.

In the Add Tests to Cycle dialog, selecting the From Another Cycle option took a long time to load the data.

Test automation tasks could not be updated to use another XML results file.

Test executions exported to CSV contained blank lines between data lines.

Other Jira applications could have problems creating linked issues if Zephyr Squad Server was installed.

Updated Atlassian libraries for the JCMA migration.

The Version search fetched incorrect results in Basic search mode on the Search Test Executions page if no specific project was selected.

The Get Audit Log API (GET /jira/rest/zapi/latest/audit) returned HTTP status 403 Forbidden for non-admin users.

The Test Executions section of issue details now has the Assignee column:

The dialog shown when changing the execution workflow status was very small. This happened when the mO SSO connector for Crowd and Jira plugin was installed and the Zephyr Workflow Validator was enabled.

On the Search Test Executions page, text in Notes contained HTML tags and entities.

Test steps having more than 10 lines could not be dragged up.

The execution history was not updated upon running an automation job for the first time.

The execution history contained incorrect timestamps.

Executions were not shown in sub-folders on the Cycle Summary page.

An incorrect message was displayed upon changing the status of a test case on the Cycle Summary page.

Execution filters did not return results in certain cases.

Project re-indexing could take a lot of time and the system resources were not released after the re-indexing was completed.

Imported custom fields with no value could have a value in Zephyr.

Archived release versions could be found in the Basic search mode on the Search Test Executions page.

Cycle names overlapped each other in the Test Execution by Cycle chart if there was too much data.

An error was posted to the log after updating or publishing the Jira workflow.