Release Notes for Zephyr Squad Cloud

Now when you install Zephyr Squad, the Test issue type is automatically added both to the default issue scheme and to the issue scheme of the existing projects.

The Test issue type is now added automatically to newly created projects.

User sessions in Zephyr Squad now remain active as long as the Jira session is active. Previously, user sessions expired after 30 minutes of inactivity.

Now if the Zephyr Squad add-on is installed in Jira, but the Test issue type is not added to your project, Zephyr informs you about this. Clicking the Add Zephyr Test issue type button in the note opens the Issue type schemes page where you can add the Test issue type to your project:

The Zephyr Custom Fields page now has a breadcrumb trail and the Help button:

Test steps are added faster now.

Sometimes, an error occurred when trying to import test steps to an existing test case.

You can now view data of Restore events in the audit log on the Apps > Manage your apps > Zephyr for Jira Cloud > General Information page.

The Test Details section now has extra space at the bottom to allow you to drag a test step to the end of the test step list:

Drag-and-drop operations are now performed faster when you move test steps within the Test Details section.

Performance improvements in the Test Executions section of test cases. All the actions are now performed faster there.

The Feedback button has moved to the Help menu:

Sometimes, an error returned when you tried to add an attachment to a test execution by using API.

A project could lose association with issue types and as a result, you couldn't work with your test cases and test cycles.

Test cases imported from Excel files were missing values for the Sprint and Affects version fields.

An error occurred in the Add Test Execution Chart by Assignee and Test Execution Burndown charts of the Dashboard upon refreshing the page.

You couldn't re-index your project, create a cycle or add a test case to a cycle after your Jira instance was under heavy load.

The edit form of the Top Defects Impacting Testing chart did not show the selected defect status after refreshing the Dashboard page.

Excessive API calls to Jira.

The Top Defects Impacting Testing gadget displayed data from other issue types instead of Bugs.

Test Automation improvements:

Improved CI/CD integration. We've created a special script to help you integrate Zephyr Squad with your CI/CD workflow without installing additional plugins. You can use this script with Bamboo, Jenkins, or any other CI/CD systems to create automation tasks and push automated test results to Zephyr after the code is built and the automated tests are executed. See Continuous Integration for details.

Improved onboarding experience:

Other improvements:

The ZAPI plugin has been deprecated in favor of the built-in REST API. Uninstall the ZAPI plugin to ensure you are accessing the built-in REST API.

Fixed re-indexing issues that caused custom fields not to work properly.

The Clear Permissions Cache button did not have immediate effect.

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

Built-in BDD support. Previously, you had to install the Cucumber for Jira app to use BDD in Zephyr – this is no longer needed. BDD support is enabled by default for all projects. You can disable BDD for individual projects in project settings.

Added timestamp options for cycles and folders in A.T.O.M to support multiple runs of a CI/CD process without overriding the current run result. Each time an automation task is executed, the cycle or folder will be cloned and named as the original cycle or folder name with the "yyyy-mm-dd hh:mm:ss" timestamp appended. The test automation API operation that creates an automation job also has the corresponding request body parameters, appendDateTimeInCycleName and appendDateTimeInFolderName, to either append a timestamp (true) or not (false).

The Search Test Executions screen now shows only the current project by default. You can use the "All Projects" filter to search in all projects.

Zephyr permissions are now controlled by Jira permissions scheme. For example:

Zephyr's General Configuration screen in Jira System Settings has a new button, Clear Permission Cache. Use this button every time after you update your Jira permissions scheme, so that Zephyr picks up the changes immediately.

No data was shown in the Daily Test Execution Progress and Executions by Date charts if you wanted to view data for the last 24 hours. The data appeared only if you zoomed in or zoomed out the chart.

Components were not sorted in the Component column on the Cycle Summary screen.

A non-admin user could access the General Configuration page via API and change settings on it.

You can now sort columns on the Manage Execution Filters page.

The column chooser on the A.T.O.M page has a new item - Executed By.

On the Search Test Executions screen, users could view and run test cases belonging to a project they had no Browse Project permission for.

You could select only the first 15 labels when adding test cases from one cycle to another.

An error occurred when trying to launch the API Keys app.

Sometimes, an error occurred upon clicking the Create a Test button.

You couldn't export a traceability report on the Traceability Matrix page if you had more than 100 issues.

The A.T.O.M page has now a search box.

The About Zephyr section has now a link to the status page where you can see the current status of Zephyr for Jira Cloud and subscribe to updates on planned maintenance.

When importing tests from an Excel or XML file, you can now skip validation to speed up the import process.

Search queries generated by links in gadgets, Cycle Summary, and in other places used the project key instead of the project name.

When adding a test to a cycle from another cycle, the Select Versions list included released and archived versions even if the Show Archive Versions and Show Release Versions options were disabled in General Configuration.

A.T.O.M jobs could not be created via API.

Introducing Next Gen project support which allows you to use Zephyr with Next Gen projects now.

Provided an option to assign a reporter to imported issues when importing test cases.

Provided alphabetical sorting for all Jira fields when importing.

Provided quality of life change that auto fills the fields when you select to use an existing saved configuration file when importing.

Improved performance for the validation state when importing.

Added a "Clear All" function for filters during searching test executions.

Fixed an issue where the drop-downs were unresponsive when you clear advanced search and switched back to basic search.

Fixed an issue where the options selected were not displayed correctly in basic search when switched to advanced search.

Fixed an issue where it would display the wrong project name in a ZQL search when you use a project name that contains the key of another project as a sub-string.

Fixed an issue where the basic search link is disabled when you click on the predefined filter "Assigned to me".

Fixed an issue where the strike-through was not displayed for associated defects that are done/closed in planning test cycles.

Fixed an issue with Total Executions and Total Executed Count deep links where if you navigated using these links, the correct executions were not being displayed.

Fixed an issue where it would not display correct data when the deep link of a cycle/folder was moved from a different version.

Fixed an issue where the exporting function would fail if the test cycle had a large amount of data.

Fixed an issue with Test Metrics where clicking on the Test Metric option would take you to a blank page with a "No Data Found" message.

Introduced the brand new internal importer where you can directly import test cases directly within the Zephyr Squad menu.

Introduced an option to allow users to schedule the tasks to be executed at future date/time in ATOM.

Introduced a clear filters option for each of the filters when searching test executions.

All selected filter options are now shown as part of the filter label when searching test executions.

Fixed an issue with fetching the correct projects when selecting the unscheduled version.

Fixed an issue around data fetching when a combination of project and multiple cycles were selected.

Fixed issues with the cycle and folder filters. The filters now only display options for the selected project.

Fixed UI issues with the date field not properly being displayed

Introduced the clear filters functionality in the Traceability matrix report that improves usability for convenience.

Introduced a feature in ATOM where the stack trace or any attachments will be added to the failed executions as part of importing.

Introduced a UX feature in ATOM that changes the task execution workflow. Now, users have an option to execute a task that requires lesser number of clicks.

Fixed a few issues around using ZBot with ATOM.

Implemented ATOM APIs for bulk deleting jobs and retrieving information on individual jobs.

Implemented bulk executing ATOM jobs within the UI.

Implemented Audit columns for ATOM jobs.

Performance Updates

Fixed minor issues with UI alignment.

Fixed minor issues with browser compatibility.

Fixed minor issues with usability.

General

ATOM

Search Test Execution

Cycle Summary

Full-featured API to interact with A.T.O.M programmatically.

Zephyr now has a new handy tool for Help, Feedback and Support links that is added to all Zephyr owned pages in Jira.

Added support for Cucumber Test framework with C4J test results (JSON file format) for A.T.O.M

Test Execution

Traceability Matrix

Test Case Summary

A.T.O.M offers you the capability to integrate and import your automated test cases from our CI/CD pipeline.

A.T.O.M supports various integration methods to allow our users to directly import the test results of their automated test cases from essentially anywhere.

A.T.O.M supports multiple test automation frameworks that are used within the testing industry.

BDD Support in Zephyr Squad

React 16 Upgrade improving the application performance

Introduced the feature to reorder test cycles and folders within the "Plan Test Cycle" page for Zephyr Squad.

Revamp of the navigation menu and its' UI to further expose all of Zephyr Squad's test functionality under the Zephyr menu.

Revamp of Zephyr Squad app permissions which limits the Test menu functionality to users within the system. This revamp allows administrators to have more control in terms of granting access to specific features of Zephyr Squad for certain users or groups of users.

Introduced an option in the general configuration settings for Zephyr Squad to display all archived versions when viewing test cycles under the cycle summary page. (Show Archive and Release Versions for Test Cycles)

Added an option to disable the appended “CLONE” text when cloning test cycles and folders under the cycle summary page. (Appending Clone Prefix Option)

Please refer to ZAPI GDPR Updates for changes on ZAPI API impacted due to Atlassian privacy API update.

Only customers emailed separately and informed on the migration for the weekend will have impact on ZAPI API and see AccountID as response. DisplayName displayed instead of UserName will be displayed on UI

Introduced single view for the test steps table and removed pagination

Lite View and Detail View

List View and Detail View on the Cycle Summary page has been improved to expand the UI for more real estate.

The default Jira menu on the left-hand side can also be minimized for more real estate.

If the characters on any of the Test Step row exceeds 200 characters, the user will need to hold the drag-and-drop until the scrollbar is visible, the user can then drag it all the way below the line separator for the step you want it to be above/below and drop it.

Custom fields added for both test steps and test executions

In-App walkthroughs to assist users with the new UI and functionality changes.

Implementation of Execution Workflows

Audit History

Toggle between two different loading methods for Testing Cycles

Dashboard Gadgets

By default, Release 3.0 uses the ADG user interface but users are able to switch back to using the old user interface (See here to switch back to the Old UI).

Quality of life changes for navigation on the Cycle Summary page.

List View and Detail View added to Cycle Summary.

Attachments allow users to preview the attachment before downloading.

Freeze columns grant the ability to ‘freeze’ two columns of test steps/test executions to scroll side-to-side without losing track. This will assist end users maintain the reference to Testcase Key/Status/Summary.

Major changes to the real estate of the Cycle Summary page and when viewing individual test executions, test steps, etc. for easier navigation.

Allow up to 20 custom fields for test executions.

Allow up to 5 custom fields for test steps.

Folder Structures: Folder Structures to support the logical grouping of test cases within test cycles.

Test Step Attachment

Enhanced UI

Introduced a new Zephyr Squad UI to coincide with the new Jira UI.

Revamped the Test Summary page by adding pagination in high impact areas such as Versions and Components. Also adding targeted search for labels.

New Cycle Summary layout improves usability and allows users to search Cycles by build, environment, description, or version.

Changed General Configuration layout and also improved Customize Execution Status and Customize Step Status pages.

Added project-level execution re-index in General Configuration.

Enhanced our ZAPI execution response time.

New Dashboard Gadgets:

Copy Test Steps from one Testcase to multiple Testcases across Projects manually and using JQL.

Bulk Associate Defects to Executions.

Bamboo Plugin made available for ZAPI Cloud.

Execution Assignment: Zephyr Squad now allows the assignment of test cases added to a test cycle.

Support for ZAPI Cloud (BETA): ZAPI (or Zephyr API) Cloud is an Add-on to Zephyr for Jira Cloud that allows access to its testing data including the ability to view and upload information programmatically.

Ability to add tests from another Test Cycle by label.

New Cloud Service status indicator.

Performance improvements in Execution Navigator and Execution Status updates.

Bug fixes.

Test Board: A new Test Board that helps you track software quality of every Sprint.

Visualization: Visualize all test executions by story; get a better sense of what has been tested and its level of quality.

Agile Sprints: The tight linking feature between the Test Cycles and Sprints now allows participation in Agile Sprints.

Quick Test Execution: The new Test Board facilities quick test execution right from within the board.

Charts: New testing burndown charts by Sprint allows constant tracking of testing status.

Sprint Quality Assessment: Assessments can be carried out with new execution reports and gadgets.

Bug fixes.

New defects can now be filed directly from a Test Execution.

A new Test can now be created from the top level Tests menu just like any other Jira issue.

Attachments can now be previewed in the Test Execution view.

Bug fixes.

Execution Navigator now has a Detailed view.

Customizable metrics are available as standard Jira Dashboard gadgets.

Links between tests and requirements/defects can now have customized linktypes.

Tests can now be added to a Test Cycle via saved JQL filters.

Bug fixes.

Two-way end-to-end Traceability tracking and reporting.

Enhanced Execution Navigator with saved searches via ZQL filters.

Column sorting in the Execution Navigator.

Bug fixes.

Ability to import tests from Excel, CSV files using theTest Importer Utility.

Enhanced Execution Navigator with Basic and Advanced search capabilities.

Advanced searching based on new Zephyr Query Language (ZQL).

Auto-completion in Advanced search.

Enhanced Remote Links – linked defects now shown in test executions and tests.

Top Defects Impacting Testing - reports.

Bug fixes.

New project-centric navigation for Test Cycle and Test Summary.

New Execution Navigator with basic search capabilities and predefined filters.

Bug fixes.

Create, view, edit, clone test cases.

Organize by project, version, components and labels.

Detailed test steps, data and expected results.

Attach files and screenshots.

Use wiki markup to edit tests.

Link to any Issue Type - Epics, Stories, Tasks, New Features, etc.

Track test coverage.

Add attachments as files or screenshots.

Create execution cycles for any iteration.

Track test execution progress.

Clone and reuse test cycles.

Execute tests either ad-hoc or from test cycles.

File new bugs or link existing ones.

Add attachments and comments.

Execute the same test multiple times or re-execute it.

File Jira bugs while in test execution screens.

Automatically link bug to testcase.

View all bugs associated with a test case across all executions.

Track daily execution metrics, test cycle and user metrics.

Trend over time.

Get Test Summary information.

Track on a per project or per release basis.