What's New in Zephyr Enterprise Release 8.6.0
January 30, 2026
Introducing Zephyr Enterprise 8.6.0. This version includes new features and improvements that will enhance your experience. Upgrade to Zephyr Enterprise 8.6.0 to take full advantage of these benefits.
Improvements
The following updates bring significant improvements and fixes:
Elasticsearch upgrade
Starting Release 8.6, the Elasticsearch version is upgraded from 8.6 to 8.18.2.
Tomcat Upgrade
Starting Release 8.6, Tomcat version is upgraded from version 10.1.39 to 10.1.47.
Java Support
Starting Release 8.6, Java 17.0.16 or later versions are supported.
Security Updates
Improved security by upgrading
Apache POI
Apache Lucene
NekoHTML
Google Guava
Protobuf-Java
Angus Mail smtp provider
Spring Framework
Spring Core
Other Improvements
Added proxy support for Jira Cloud integration.
Authentication and SSL Support for JobRunnr integration and SSL Support for JobRunnr integration.
Support for attachment through API.
Support for API Traceability.
Bug Fixes
The following table lists the bug IDs, fixed issues, and error resolution.
Bug ID | Resolution |
|---|---|
ZEPHYR-20672 | Fixed an issue where the Export filter options in requirements displayed all organization users instead of limiting the list to users assigned to the selected project. |
ZEPHYR-35669 | Fixed the error that occurred when deleting the cycle phase during bulk execution. |
ZEPHYR-39072 | Fixed an issue where the Epic Link dropdown list was not displaying for Jira epics. |
ZEPHYR-43672 | Fixed an issue where the tooltip displayed on mouse hover caused the screen to flicker in the cycle phase of Test Planning. |
ZEPHYR-43719 | Fixed the issue in Jira integration by adding logic to schedule access token renewal when editing an existing OAuth2 Jira integration without changes. |
ZEPHYR-39227 | Fixed an issue that prevented importing Jira requirements when the requirement name included an emoji. |
ZEPHYR-39700 | Fixed the issue where users could create duplicate Release, Cycle, and Phase items with identical names. Validation now exists at both the user interface and API levels to prevent duplicate names for Release, Cycle, and Phase. |
ZEPHYR-41101 | Fixed the issue with filters in Advanced Search. All filter options now appear in the list. |
ZEPHYR-41561 | Fixed the issue where searching for Empty and Not Empty values with a custom field returned incorrect results. |
ZEPHYR-41963 | Fixed the issue where requirement traceability did not display when a Jira defect was mapped as a duplicate. |
ZEPHYR-41588 | Fixed the issue where the audit log export did not include all records. The exported CSV file now matches the number of entries displayed in the user interface. |
ZEPHYR-42681 | Fixed the issue where full indexing failed when database tables contained large string values exceeding 20 million characters. Jackson no longer throws a JSON parsing error during the indexing process. |
ZEPHYR-42835 | Fixed the issue by adding data validation to prevent null values when creating a Release. |
ZEPHYR-42845 | Fixed the issue where test step details were missing from the first export file when opening the file in Excel Online. |
ZEPHYR-42851 | Fixed the issue where the assigned name was not updated in Test Execution. |
ZEPHYR-42886 | Fixed the issue where Jira comments were not visible in specific scenarios on the Defect Tracking page. Comments now display correctly when viewing defect details. |
ZEPHYR-43049 | Fixed the issue where users could not remove requirements from test cases after saving. When cloning a test, associated requirements were copied and could not be removed or updated. |
ZEPHYR-43050 | Fixed an issue where the Tag column was missing in the Test Planning section. The column now appears as expected. |
ZEPHYR-43063 | Fixed the issue where the release dropdown appeared empty in Zephyr projects with more than 2,100 releases when using MSSQL. The release list now displays correctly without errors. |
ZEPHYR-43262 | Fixed the issue where sorting the dashboard by ID did not work as expected. |
ZEPHYR-43270 | Fixed the issue by improving the process of migrating attachments from internal storage to external storage. |
ZEPHYR-43321 | Fixed the issue by including the "Unexecuted" status in the Zephyr Enterprise Jira plugin. |
ZEPHYR-43311 | Fixed the issue where disabling the lower_case_table_names configuration on MySQL prevented Zephyr from locating certain tables due to case differences in Hibernate mapping. This caused user operations to fail with related errors. |
ZEPHYR-43354 | Fixed the issue where cycle names and phase names showed the server time zone instead of the local time zone when uploading test cases through the API. |
ZEPHYR-43357 | Fixed the issue by updating user details in the application to display first name and last name instead of username. |
ZEPHYR-43375 | Fixed the issue where enabling the "Create Package Structure" option in Jenkins created duplicate folders in the Test Repository section. |
ZEPHYR-43584 | Fixed the issue where moving a cycle phase with no test cases to another cycle caused test step result data loss. |
ZEPHYR-43614 | Fixed the issue where defect creation and updates failed through the UI and API. Optimized the code to improve reliability and handle failure scenarios correctly. |
ZEPHYR-43739 | Fixed the issue for Patch_0208_mssql.sql and Patch_0209_mssql.sql, which contain a hardcoded database name for MSSQL. |
ZEPHYR-43741 | Fixed the issue where large cycle data triggered Elasticsearch errors, causing the application to hang. |
ZEPHYR-43785 | Fixed the issue that prevented editing cloned test cases created from BDD test cases. |
ZEPHYR-43814 | Fixed the issue where users were unable to create a defect for the Jira project. |
ZEPHYR-43951 | Fixed the issue in the Test Case Execution Progress report where phases exceeding 1,000 caused execution failures. Updated the application logic to prevent exceeding Oracle database in-query limits. |
ZEPHYR-43957 | Fixed the issue where the release cloning process failed due to an Oracle database limitation. Updated the application to split large IN-clause queries into multiple batches of 1,000 values or fewer. |
ZEPHYR-43972 | Fixed the issue that allowed renaming multiple custom fields or adding values unintentionally. You can rename only one custom field or add values to a single custom field at a time. |
ZEPHYR-43977 | Fixed the issue where the ZE API endpoint create-and-execute-job created duplicate executions for a single POST request. |
ZEPHYR-43985 | Fixed the issue where indexing mismatches occurred after executing test cases. |