What's new in 12.60.52 (SaaS)

The following new features and enhancements are introduced in ALM Octane version 12.60.52.

Enterprise agile

In the team story board, if you filter out a backlog item type, the phases or sub-phases that belong exclusively to the filtered-out type are removed from the board.

For example, if you exclude defects, the Proposed Closed sub-phase is hidden.

Quality enhancements

The following testing enhancements are now available:

  • When running automated tests using test runners, the administrator can now configure predefined sets of parameter values to be used by testers in different suite runs. For details, see Working with parameters in test runners.

  • When you are running a test suite with automated tests on Jenkins, you can now stop the run from within the ALM Octane UI. For details, see Stop automated tests in a suite run.

  • Automation of Gherkin tests now supports Cucumber 4.2. For details, see Automate Gherkin tests.

Back to top

Administration

The logic for calculating a suite run status based on its test run statuses is now defined by out-of-the-box business rules. For details, see Set up rules.

Changes in behavior

Note: The following changes are being implemented. These changes might necessitate some action on your part.

  • The Integration Bridge method of creating Webhooks has been replaced by the WebSocket communication method. If you have rules that communicate via an Integration Bridge, create replacement rules using WebSockets. For details, see Trigger webhooks for other applications.

  • When creating or editing a list, you will no longer see the internal logical names of lists and list items by default. Similarly, filtering is now done using the external names of list items, rather than by internal logical names.

    For backward compatibility, if you need to see logical names in the UI you can activate the parameter ALLOW_SETTING_LIST_NODE_LOGICAL_NAME, which restores the previous behavior.

Back to top

REST API

For a list of REST API changes, see What's changed in the REST API.

Back to top

See also: