What's New in Zephyr Enterprise 8.1.0

July 19, 2024

 

Introducing Zephyr Enterprise 8.1.0. This version includes new features and improvements that will enhance your experience. You will benefit from better performance, increased efficiency, and advanced tools to manage your projects more easily. Make sure to upgrade to Zephyr Enterprise 8.1.0 to take full advantage of these benefits.

Starting Release 8.2, Zephyr Enterprise documentation is moving from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise Documentation page. This transition aims to provide a more user-friendly experience with improved navigation, enhanced search capabilities, and a more intuitive interface. We appreciate your patience during this transition and look forward to providing you with a better documentation experience.

Important Announcements

  • Restart the MySQL database before upgrading to Zephyr Enterprise release version 8.1.

  • By default, Jira sync is disabled for any release that has reached the end date or does not have a defined end date for accurate syncing.

  • Starting with the Zephyr Enterprise release version 8.1, it only supports Jira Plugin version 1.8.8 or later.

  • Starting Zephyr Enterprise release version 8.1, the following Jenkins versions are supported:

    • Jenkins version 2.452.1 or later.

    • Zephyr Jenkins version 2.9 or later; note that Jenkins deployment requires Java 17.

  • Starting from Zephyr Enterprise release version 8.1, support for the following has ended:

    • Oracle 12c

    • CentOS 7

New Features

The following updates bring significant enhancements, security improvements, and fixes:

Java 17 Support

Release 8.1 now supports the latest Java 17 or OpenJDK 17.0.10 versions. You can download Java 17 and OpenJDK 17.0.10 from the respective download page. Users must use Java 17 when using ZBot on their server.

OAuth 2.0 Webhook Support

Starting Release 8.1.0, Zephyr Enterprise will support the integration of RabbitMQ with OAuth 2.0 which represents a significant advancement in messaging system security and user authentication. The OAuth 2.0 backend plugin for RabbitMQ supports JWT-encoded access tokens, enabling a more precise and controlled access management system.

Webhook Windows Operating System Support

Release 8.1 now supports new enhancements for the Zephyr Enterprise Webhook Module.

Decoupling - The webhook system is now a standalone runtime, separate from Zephyr Enterprise (ZE). This allows asynchronous processing of JIRA events independent of ZE resources.

Centralized Queue Management - Transitioned from file-based to RabbitMQ queuing for better scalability and flexibility. RabbitMQ user panels provide visibility into event processing, queue status, and traffic trends.

Fault Tolerance - Implemented persistent queues for data integrity and reliability. Developed handshake and retry mechanisms to handle service failures and comply with JIRA rate limits.

Enhanced Audit Logs - Improved system to capture comprehensive logs and audit trails for webhook processing.

Rich Text Editor Tab

In this release, you can use the Tab key to move to the next option on the UI, which simplifies text editing and formatting for users.

Password Encryption for ZE Services

In the latest update, we have successfully encrypted the passwords for MySQL, MSSQL, Oracle databases, and RabbitMQ to enhance security. This upgrade impacts both ZE-RabbitMQ Consumer and ZE-Audit-Processor.

External Storage Improvement

In Release 8.1.0, the external storage options for both AWS S3 and IBM Cloud Object Storage (COS) have been enhanced.

Use Existing Bucket Names

You can now use an existing bucket name for external storage, reducing the need to create a new bucket name.

Custom Deployment Options

For IBM COS deployments within your network, non-IBM COS cloud deployments, and custom deployments, you can now select the "Custom" option from the list. This allows you to deploy changes by specifying the URL, providing seamless integration with your existing infrastructure.

Fixed

The following table lists the bug IDs, fixed issues, and error resolution.

Bug ID

Resolution

Bug ID

Resolution

ZEPHYR-38868

The current Drill Down report has been updated to allow users to sort test execution progress data alphabetically by name, like the Planning view, making it easier for reference and comparison.

ZEPHYR-39252

The issue with the description field in the “requirement_tree” table storing JQL longer than the 1024-character limit defined by the schema table has been fixed. Now, when synchronizing requirements from Jira into Zephyr, the description field correctly accommodates the JQL and its date.

ZEPHYR-39251

In the current release, issues related to bulk edits to the custom field can now be performed successfully without errors.

ZEPHYR-38039

In release 8.1, the issue related to the "Unable to create temporary attachment directory" error when publishing test results to Zephyr using Jenkins pipeline jobs is now resolved. The following versions are supported in this release:

  • Jenkins version 2.452.1 or later

  • ze-jenkins plugin version 2.9 or later

  • Jenkins should be deployed using Java 17

ZEPHYR-37992

The issue where the text field editor opens excessively large, causing half of the table to move out of view and resulting in missed clicks, has been resolved. These fixes have significantly improved the process of adding test steps, making it much smoother and more efficient.

ZEPHYR-39250

In the latest update, we addressed the issue of execution count mismatches between the Elasticsearch (ES) and the database (DB), which was causing inaccurate data to be displayed. As part of the fix, a synchronization process is implemented between ES and the DB to ensure consistent and correct data is displayed.

ZEPHYR-38761

The performance issue with the dashboard on the SQL Server database, which was not performing optimally, has been fixed. The query has been modified to enhance the dashboard's performance.

ZEPHYR -39228

In the current release, the issue related in creating the webhook, project, and version events is fixed. Clicking "Update Webhook," the existing webhook will be updated to exclude project and version events.