Version 9

The test execution list now displays properly without being compressed.

Importer no longer gets stuck when Excel files contain data like /* sometext /*. You can now restart imports even after canceling a previous one.

The Zephyr Importer now correctly uploads test cases when the "Due Date" field is mandatory.

Test Automation now accepts Eggplant test result files.

Fixed a project ID issue where disabling a project (e.g., 114501) mistakenly affected others with similar IDs (e.g., 11450 or 14501). Now, only the intended project is disabled.

Improved Jira Data Center support by enabling autoscaling nodes to sync Zephyr indexes faster. New nodes now perform delta reindexing using the latest available backup, reducing downtime and ensuring smoother transitions.

Exporting HTML with attachments or any format in Search Test Executions now works even if the project name, key, or ZQL fields like components include the & character.

Bulk actions on the Test Executions page now work even if the project name or ZQL query includes special characters like & or +.

Increased memory check for imports to 90% with a configurable option. You can now adjust it between 80% and 90%, or disable it entirely.

Upgraded jackson-core library to version 2.15.0 or newer for improved compatibility and security.

Improved the header alignment when viewing Version details with Zephyr Squad enabled. The display is now clear and properly organized.

Resolved a vulnerability (CVE-2022-42889) in Apache Commons Text that could lead to arbitrary code execution.

When removing the ZQL-query from the Search Test Execution (STE) page, users were able to update the bulk status for all selected tests, impacting all active projects without proper error handling. The ZQL-query box now blocks bulk status updates when empty. An error message will display, or the “Tools” dropdown will be disabled to prevent unintended updates.

We fixed Alert of a possible vulnerability to SQL Injection.

Fixed an IDOR vulnerability in Zephyr 9.5 under Jira DC 9.12.8, which allowed unauthorized access to attachments via the /jra/plugins/servlet/schedule/viewAttachment endpoint. This security issue was resolved to ensure proper access control and prevent unauthorized data exposure.

Fixed an issue where the Zephyr Squad plugin caused incorrect date formatting in Jira (non-English languages). Now, when Jira is set to a language other than English (e.g., Spanish), date fields on certain pages display correctly without causing errors.

Fixed an issue in Jira 9.13.1 with Zephyr Squad where filters (Priority, Execution Status, Component, Label) were not working when adding tests from another cycle. Now, you can easily pick and add test cases using these filters as expected.

Fixed an issue where exporting test cycle data with multiple folders and large datasets caused a timeout error. Also, the selected color in a custom field is now updated automatically when adding a new color.

Visiting a Test Case in the Activity tab now only shows relevant entries. Previously, refreshing the page created extra link entries without any changes being made.

The Zephyr Test Execution Progress gadget now displays "Other" status correctly in both columns when added twice to a two-column layout.

Cycle names with double or multiple spaces now display correctly in the Cycle Summary UI. They will show exactly as entered, without trimming to a single space.

The cleanup cycle progress indicator now stops spinning when the task completes successfully. You no longer need to refresh the page to see the update.

When you add tests to a cycle from the Jira "Search Issues" page, the Estimated Time didn’t show up in the Execution page. Now, after adding test cases, the Estimated Time should display correctly based on what you set when creating the test case.

Users can now import test cases with multi-select custom field values that include commas. This change allows the system to correctly assign values from an Excel sheet during the import process.

The execution page will show the correct estimated time for test cases added to a cycle through the JIRA Search Issues page bulk change option.

We implemented a feature to selectively reindex only missing executions, ensuring continuous system availability and less disruption during the reindexing process.

Deleting the write.lock file during re-indexing operations in a Jira Data Center environment was causing nodes to enter maintenance mode and preventing further re-indexing. This issue has been fixed, ensuring that nodes no longer enter maintenance mode unnecessarily, and re-indexing operations can be performed successfully across all nodes.

We reduced the number of calls to fetch the summary of test executions linked to issues, improving CPU usage and reducing the frequency of indexing calls in customer environments.

We reduced the number of threads and database calls when fetching cycle summaries via the REST API, improving efficiency and stability in customer environments. This includes querying the database directly for summaries to minimize load.

The Retrieve button for import mapping is now functioning as expected, ensuring correct retrieval of mapping fields.

We resolved an issue where a specific test step was missing in Zephyr Testcases if the cursor was placed on that step and the "Create" button was clicked. After creating the test case, all added steps appear correctly in the Test Details section.

The Gadget legend is now visible in the latest versions of Jira with Zephyr Squad.

The date format is now correct after fetching results from Jira using JQL.

The newly created test step is not deleted while reordering it.

You can now edit time tracking value in Jira 9.x after selecting a Test on the Issue page.

We fixed the encoding issue in the Search Test Execution export functionality, ensuring that special characters in test names and cycle names are correctly displayed across all languages in the exported Excel/CSV files.

We fixed an issue where changing the language in Jira did not update the language on the execution page.

Resolved multiple library vulnerabilities identified through GitHub scans by updating dependencies in both Jira 8.x and Jira 9.x, with a preference for Jira 9.x due to the upcoming end-of-life of Jira 8.x.

You can now estimate the migration time with and without Audit history in Cloud migration.

We fixed issue with index job getting stuck on restarting of Jira nodes in DC.

You are now able to auto-retry sync on timeout or failure during indexing.

After refreshing the browser, the checkbox  “Enable selection of all executions (Admins only)”no longer remains selected and can be deselected, allowing the user to change the selection status.

The "Executed By" value now displays the full name or username on the Execution history page instead of user Jira ID.

You are now able to auto-retry sync on timeout or failure during indexing.

We upgraded log4j from 1.x to latest version. You can navigate to the "log" folder in the Jira app directory and view the log4j files.

Now when you work on settings in the General Configuration page as a Jira admin, you can see the project which is adding a "Projects by Filter" search field. The pagination works correctly when adding more projects.

Links for Test and Requirement in the Zephyr configuration page are working as expected.

The data in the Test Summary page is showing now on the graphs.

We added an option to switch an instance to Squad 1.0 from Squad 2.0.  Check our JCMA Guide to learn more. For customers migrating from On-Prem to Cloud, the old experience will be the default.

Due to the end of the support for Atlassian Server apps in February 15th, 2024, we provided necessary information about migration paths and possibilities. Just open the Zephyr Squad application and you will see the banner leading to all relevant sites.

The server instance can display the total number of objects now.

Due to the end of the support for Atlassian Server apps in February 15th, 2024, we provided necessary information about migration paths and possibilities. Just open the Zephyr Squad application and you will see the banner leading to all relevant sites.

We implemented app migration retry for only Zephyr data. In case Jira migration is successful and Zephyr fails, this option helps with only migrating plugin data. Re-run appears only when the migration status is Failed or Incomplete.

As part of our continues effort to make Zephyr Squad better for our users, we enhanced the performance of migration to the cloud process.

We added the following fields to the summary of JCMA migration for one plan: serverPluginVersion, skipAudit, uploadTime.

As part of our ongoing efforts to make the use of Zephyr Squad more efficient for our users, we introduced the ability to migrate data from one instance to another using the backup and restore feature. Find out more: Backup and restore

Datacenter check is removed for users with server licenses that navigate to Cloud Migration.

You can import the cascading custom field values via Zephyr Tests without the error.

Now only users added to the specific project appear in the search for that project.

Modified the execution count calculation while applying sync.