Version 5

Release 5.6.5 (December 2, 2020)

Improvements:

Bug fixes:

  • Sometimes, audit history queries caused performance issues.

  • The Test Executions section of a test case could not be expanded if the test was linked to a web page.

Release 5.6.4 (November 11, 2020)

Improvements:

  • A.T.O.M has been renamed to Test Automation.

    Test automation menu
  • The Create Automation Task dialog now properly reflects custom required fields configured in your Jira instance. Also, we've redesigned this dialog to match the Jira UX style.

  • In sprint view, you can now search for folders as well.

  • When editing test steps, you can now use the wiki markup visual editor to edit step contents.

  • In the Bulk Assign Executions dialog (Search Test Executions -> Tools -> Assign Executions), the Save button has been renamed to Assign, and the default value of the Assigned To field is now Unassigned.

  • When configuring Zephyr Custom Fields, you can now delete multiple fields at once.

  • Custom Fields API has a new operation to bulk delete multiple fields:

    DELETE /rest/zapi/latest/customfield/delete-customfields

    Content-Type: application/json

    { "customfields": ["3", "14"] }

Bug fixes:

  • The Test Execution Time Tracking gadget showed the total estimated time and the total logged time in wrong fields if all cycles had been selected.

  • The Test Execution gadget did not display the names of some cycles.

  • 30 Day summary charts in the Test Summary were not loading in Jira Data Center edition.

  • A user could copy test case steps on the Copy Zephyr Test Steps page even if they had no permission to access the test case.

  • Test cases could not be imported if more than 50 issue types were associated with the project.

  • Test cases could not be imported if the Zephyr Teststep field was a required field.

  • The required Epic Link was not shown as required on the Importer screen, and an error occurred when importing a file.

  • The Executed On value of test executions displayed wrong time if the user's time zone was different from the Jira server time zone.

  • The Add Tests To Cycle operation in Jira's Bulk Change wizard displayed projects to which the user did not have access.

Release 5.6.3 (October 5, 2020)

Version 5.6.3 fixes wrong text wrapping in test step fields.

Release 5.6.2 (September 7, 2020)

Compatibility with Jira Server/Data Center 8.12.x.

Release 5.6.1 (August 8, 2020)

Improvements:

  • You can now rename step-level attachments when pasting them by using Ctrl+V (on Windows) or Command+V (on Mac).

Bug fixes:

  • An error occurred when adding a default value for the Zephyr Teststep field in Administration -> Issues -> Custom fields.

  • Step-level attachments were not displayed after moving a test case from one project to another.

  • In Test Details, text enclosed in square brackets was displayed on a separate line.

  • A test with a custom field could not be imported if that field had different custom field configuration schemes in Jira.

Release 5.6.0 (July 21, 2020)

Improvements:

  • REST API is now available out-of-the-box. The ZAPI plugin is no longer required to access the API.

  • Compatibility with Java 11 and OpenJDK.

  • The A.T.O.M page now remembers the column selection and sort order. These settings are preserved for each project.

  • Execution History now includes information about attached files.

  • The order of test cases is now preserved when adding test cases from one folder to another by using the From Another Cycle option.

  • The Comments field in test steps is now resizable and supports Jira wiki markup.

Bug fixes:

  • The maximized Test Details window had extra whitespace if you had unselected some items in the column chooser.

  • It was impossible to import an Excel file if a column header name contained special characters.

  • Pressing Tab didn't move the cursor to the right in the row of existing test steps in the Test Detailswindow.

  • If you imported a test that had the Select List (cascading) custom field, the imported test did not have that custom field.

  • Test step data was overlapped when the Test Details window was expanded.

  • It was impossible to edit execution-level customs fields if all the steps of a test case were marked as passed.

  • You couldn't retrieve file mapping in the internal importer if Jira had been installed with Java 11.x.

  • Test cases imported from an XML file contained extra XML tags in the test details section and in custom Jira fields.

  • Incorrect number of unexecuted tests in the Test Execution Burndown gadget.

  • The Comment field on the Test Execution page was shrunk to half width during editing.

  • In projects with custom workflows, transitioning a test case to a new status caused the web page to become unresponsive.

  • In Internet Explorer and Edge, test executions were always exported to a text file format instead of the chosen format.

  • If project settings had a page whose URL contained the # character (such pages are added by some plugins), navigating to that page caused the Jira sidebar menu to disappear.

  • "Error retrieving license information" errors in zephyr-jira.log when accessing the A.T.O.M page if the ZAPI plugin was not installed.

  • An error occurred when importing tests if the Jira Create Issue screen had more than 50 fields.

Release 5.5.5

Bug fixes:

  • Fixed: An issue with latency in fetching executions on the Plan Cycle Summary page.

  • Fixed: The previously attached files were not visible, or users could not attach new files at the test step level.

  • Fixed: ZAPI APIs did not return the expected results when the corresponding Jira server was set up in a non-user interactive mode.

  • Fixed: The A.T.O.M date format was incorrect upon modifying the date in the execution history.

  • Fixed: Zephyr affected rendering of non-Zephyr pages in Jira.

Release 5.5.4

Features:

  • The execution count and pagination summary have been implemented within the ATOM page.

  • Introduced auto-scrolling which is now available for dragging and dropping cycles/folders in the plan test cycle page.

  • Provided an option to disable the Test View option after disabling a particular project.

  • All attachments will now have 3 different options available when viewing it in the preview window.

    • Added Zoom In, Zoom Out, and Fit to Screen.

  • Zephyr will now save or retrieve the column choose selection as per the user preferences in the ATOM pages now.

Performance:

  • Improved the performance for all project re-indexes.

  • Provided CDN Support for DC setup in Zephyr for Jira.

Release 5.5.3

Bug fixes:

  • Fixed an issue with step level test executions not being properly displayed.

Release 5.5.2

Features:

  • Provided a mapping option to add requirements/story Jira issue ID while bulk importing the test cases.

  • Provided a new ZFJ Server video available in the Welcome page.

  • Added the column choose for ATOM to allow users the ability to choose which columns are displayed.

  • Added the audit columns for ATOM for usability improvements and convenience.

  • Minor improvements made to enhance the usage of the importer utility.

Performance:

  • Improved execution performance for tests from the database and indexes.

  • Compatible Jira versions updated.

    • Server Compatibility: Jira versions - 8.0.x to 8.8.0, Jira Enterprise version - 8.5.4

    • Data Center Compatibility: Jira versions: 8.0.x to 8.8.0, Jira Enterprise version - 8.5.4

Bug fixes:

  • Fixed an issue with the internal importer where if an issue type was set to "Test" and the test was not assigned to a project, it will throw an error.

  • Fixed a UI and usability issue with ATOM's column sorting and pagination.

  • Fixed an issue with Kanban boards regarding the "Test" view.

  • Fixed an issue that caused an error while importing with links while using the importer tool.

  • Fixed some issues with the time tracking field.

  • Fixed an issue with the default Jira status colors changing when Zephyr is newly installed.

  • Removed the limitation on number of ATOM tasks that can be created. The current limitation of 1000 was removed.

Release 5.5.1

Features:

  • Added additional flexibility to the internal importer.

    • Admins can restrict the file size to be imported to ensure large files being imported are not affecting the Jira instance.

      • The limit can be set by an admin and is applicable for all import sessions.

    • Removed other issue types from the importer to allow users to import issues of type TEST.

  • Provided an option to Enable/Disable A.T.O.M functionality using ATOM specific permissions at a project level.

    • It is enabled for everyone by default.

Bug fixes:

  • Fixed issues with the compatibility of the Atlassian Createmeta API due problems with the importer displaying all fields.

  • Fixed an issue with the Test Distribution Gadget which showed incorrect data for the test data for "Group by Configuration".

  • Fixed an issue with re-ordering feature for the Test Executions Details gadget.

  • Fixed a few browser specific issues with the alignment and a few cosmetic issues causing functional integrity.

  • Fixed a few minor issues with A.T.O.M.

Release 5.5.0

Features:

  • Introduced A.T.O.M which provides users with the capability to integrate and import their automated test case results.

    • Also known as Automation Testcase Organizer and Manager (A.T.O.M).

    • Users can easily import, organize, and manage their automated test case results.

    • A.T.O.M supports multiple integration methods and various automation frameworks that can be used as well.

  • Allowed users to view the test execution even when the status (workflow) is set as Done when time tracking is enabled.

    • Users can now preview the individual defect(s) that is linked to the test execution when the status is set as Done.

    • Users can preview the attachments for the test execution.

    • Users can preview the attachments for the test steps but not the linked defects in the test execution.

  • Zephyr help, feedback and support links added to the Zephyr Test menu in the top-level navigation.

  • Added the 'All cycles' and 'All folders' option for the cycle field in the Test Execution Time Tracking gadget.

    • This allows the user to select all test cycles and folders for the selected versions when using this gadget. Previously, users would have to select test cycles one by one and now they can select all cycles/folders at one time.

    • When selecting the 'All cycles' option, it will display the cycles grouped with its' folders in the gadget view.

    • Users is provided with the 'All folders' option when a cycle is selected.

Bug fixes:

  • Fixed a few issues around the "Search Test Execution (nav)" page.

  • Fixed a couple of issues around cloning test steps and using the bulk clone option.

  • Fixed various issues around the Zephyr Importer, we have made the import tool more robust now as more and more customers are migrating to Zephyr and are using the importer tool to bring their test cases from other systems to Zephyr.

  • Fixed some issues around the Time Tracking gadget and enhanced the functionality to make it more user friendly.

  • Fixed an issue with the Execution Details gadget related to ZQL.

Release 5.4.1

Zephyr for Jira 5.4.1 and above is now compatible with the updated Jira versions 8.0.x to 8.6.

  • Compatibility with both Server and Data Center.

  • Zephyr for Jira now supports PostgreSQL version 10.0.

Bug fixes:

  • Fixed an issue with JQL allowing users to search and filter with the new version (fixVersion = "5.4.1").

  • Fixed an issue where the maintenance mode was not resetting. This occurred when the node that initiated the re-index would be restarted midway during the re-index process.

  • Fixed an issue where it is not correctly setting the heartbeat when the Jira is not shut down correctly as a result of an unnecessary sync job triggered.

Release 5.4.0

Introduced the Reorder Test Cycle and Folder option to allow users to reorder both their test cycles and folders within the test cycle summary page.

  • The feature can be enabled in the Zephyr for Jira general configurations page.

  • Test cycles and folders can be sorted and ordered using the creation date or name of the test cycle/folder.

  • Test cycles and folders can be sorted and ordered using a custom reorder which allows users to utilize a drag and drop feature to personally reorganize their test cycle/folder however they want.

Release 5.2.2

Bug fixes:

  • Fixed the issue with the Zephyr Test menu not appearing after upgrading the product. This issue was specifically for customers who had previously disabled the Test menu for one or more projects.

  • Fixed an issue with ZAPI being unable to report the job progress when the Zephyr cluster was in maintenance mode due to a hard re-index.

  • Fixed an issue with being unable to search by labels in the execution’s navigation view.

Release 5.2.1

Features:

  • Introduced an option to customize the message that is displayed when Zephyr goes into maintenance mode.

    • This new option is available within the general setting menu under the Zephyr settings

  • Provided an option to enable and disable the orphans clean-up job that was causing CPU spikes.

    • By default, the orphan's deletion job is disabled and does not run every 12 hours.

Bug fixes:

  • Fixed an issue with attachments appearing twice within the Jira instance when using a Chrome browser.

  • Fixed an issue with the alignment of UI elements being visible in various views when using an Edge browser.

Release 5.0 (Jira 8.0.x Compatibility)

  • Zephyr for Jira 5.0 is now compatible with Jira 8.0.x and above.

  • Zephyr for Jira 5.0 is not compatible with Jira 7.0.x and below.

  • Zephyr for Jira has made changes to the Jira Index Folder Structure location and the library upgrade.

    • Customers that plan to upgrade to this build should plan to upgrade during a time when a hard reindex can be performed.

    • Hard reindexing is a mandatory function after upgrade to Zephyr for Jira 5.0.

Known Issue(s)

  • Users may experience an error when recovering indexes of old backup files. This applies to the index recovery in Datacenter for version 5.4.1.

    Important

    Hard reindexing is a mandatory function after upgrading to Zephyr for Jira 5.0.

Publication date: