What's new in 12.55.17 (CP6)

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

On-premises: For other enhancements in the 12.55.17 on-premises release, see also: What's new in 12.55.13 (CP6) and What's new in 12.55.9 (CP6).

What's new video

Watch the What's new video:


The following usability enhancements are now available:

Improved release context filter

The Backlog module’s release context filter has been improved. When you filter by release, you now see all of the features related to the release. A feature will displayed in the filter if either the feature itself is assigned to the release, or if any of its backlog items are assigned to the release.

To display only features that are assigned directly to a release, you can add a filter condition.

Other enhancements include:

Enhancement Details
Copying defects to a different workspace

Users with access to more than one workspace in a shared space can copy defects between the workspaces.

Exporting requirements to Word or PDF

You can export requirements to Word or PDF files. ALM Octane creates a Word or PDF file of the selected requirements tree.

For details, see Export requirements to Word and PDF formats.

Deleting entities

You can now delete an entity from within its Details view.

Exporting images

You can now export a Dashboard widget as an image. ALM Octane downloads the widget as an image file.

Limitation: Not supported in Internet Explorer 11.

The following fields have been renamed:

Original name New name
Last Runs

Test Coverage (except in the Tests tab)

Covered Content Backlog Coverage

Back to top


The following enhancements are now available in the testing areas:

Use Sprinter to run manual tests

You can now run your ALM Octane manual tests in Sprinter. Supported with Sprinter version 14.03 and above.

For details, see Run and edit manual tests in Sprinter.

StormRunner Functional support

StormRunner Functional has been added to the list of automated testing tools, in addition to StormRunner Load.

  • Use the StormRunner Functional value when configuring a pipeline step, to set the testing tool for all future test runs from that step.

    For details, see Configure steps: Define test and test run information.

    Tip: When using API, entities might still include the testing tool value StormRunner. This refers to StormRunner Load.

  • When ALM Octane receives StormRunner Functional test runs from a pipeline that ran on Jenkins, it automatically marks the testing tool as StormRunner Functional, even if you did not configure the pipeline step.

    This requires version 5.3.3 or later of the Application Automation Tools plugin, currently available as a beta version.

Copy manual test run steps to defects

When creating a defect from the Manual Runner, you can now copy the test run steps to the defect's description field.

For details, see Report defects during a run.

Back to top

Pipelines and CI servers

We have made the following Pipeline and CI improvements:

Microsoft Team Foundation Server (TFS) 2017 supported as a CI server

Set up integration with TFS as a CI server. Track build and test results from your TFS build jobs, as well as SCM commits, as part of your release progress and quality in ALM Octane.

For details, see Install and configure the ALM Octane CI plugin on your CI server.

Automatic Build Failure Classification (technical preview)

  • Create rules that map Jenkins build log messages to the failures they indicate. For details, see Analyze builds.
  • ALM Octane automatically classifies build failures by analyzing log files.
  • Add the Pipeline build failure classification cumulative widget to your pipeline's dashboard to see the main reasons for a pipeline’s failures over time.

Use test clustering to accelerate pipeline run failure analysis (technical preview)

ALM Octane clusters failed test runs based on failure similarity. Group the runs in the Failed Test Runs tab by cluster.

  • The number of clusters can give you an idea of the number of problems that need to be fixed.
  • When analyzing failing tests in your pipeline run, start with the large clusters. Fixing one failed run in this cluster is likely to fix all failures in the cluster and significantly reduce the number of failures in the next run.
  • When assigning a failed run to someone for handling, you can assign all of the failures in the same cluster to the same person.

For details, see Test run details.

Improved user interface on the main Pipelines page

  • Configure your pipeline overview widgets

    The fixed pipeline run overview has been replaced by a configurable dashboard. Choose from the available widgets in the DevOps & Analytics widget gallery or create your own widgets.

    The Details tab for a pipeline now shows more information about the pipeline's definitions. It no longer includes summary widgets about the pipeline's latest runs. These are available in the Pipelines dashboard.

  • Improved recent pipeline history widget

    We simplified the look and feel of the pipeline's timeline, available under the Recent Pipeline History drop-down.

    Click any column in this widget to open a specific pipeline run for further investigation.

Back to top

Fortify on Demand (technical preview)

We have made the following enhancements to the Fortify on Demand integration:

  • The Fortify on Demand vulnerabilities are now linked to committed code changes. This helps committers find vulnerabilities their commit might have introduced.

  • If your Fortify on Demand server is currently available, each vulnerability displays additional information from the security assessment that can help you fix the issue.

  • When creating a pipeline that includes a Fortify on Demand job, you must now select the Security pipeline type.

    If you previously created a pipeline with a Fortify on Demand job, add Security to its Type field to see the Vulnerabilities tab. (ALM Octane > Pipeline > Details tab)

For details, see Track security vulnerabilities.

Back to top

Settings and configuration

The following configuration enhancements are now available:

Shared customization

Customize user-defined fields and workflows on both a shared space level for all associated workspaces, and for individual workspaces.

Shared workflows can also be modified on a workspace level.

For details, see Sharing UDFs between spaces and Sharing phases and workflows between spaces.


You can define credentials so that ALM Octane can access applications that require basic authentication. You can specify credentials in a Call URL rule.

For details, see Set up credentials.

Call URL rule enhancements

  • ALM Octane supports basic authentication in Call URL requests.

  • Customize the request payload by selecting additional fields to include.

  • SaaS:  You can now send direct HTTPS or HTTP POST requests by setting the new configuration parameter CALL_URL_ALLOW_HTTP.

Other enhancements include:

Enhancement Details
User-defined fields (UDFs)

Memo fields are now supported.

Deactivate releases When you finish working on a release, you can deactivate it. Deactivated releases no longer appear on lists of data entry, such as assigning content to a release. However they do appear in filters, so you can see which content was assigned to obsolete releases.

Back to top

IDE plug-ins

The following enhancements are now available for IDE plugins.

Visual Studio

The ALM Octane plugin for Visual Studio can now connect to ALM Octane using SaaS federated accounts.

For details, see the documentation for: Visual Studio

Back to top


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

Back to top


The following enhancements have been introduced for on-premises installations:

Enhancement Details
License sharing with Quality Center

Quality Center licenses can now be shared with ALM Octane Pro Edition.

For details, see Manage licenses (on-premises).

Windows installation The ALM Octane installation on Windows now includes upgrade and rollback options.
Notices on login page Admins can now add customized notices, such as GDPR conditions for consent, terms, and disclaimers, to the ALM Octane login page using the LOGIN_PAGE_NOTICE configuration parameter. For details, see LOGIN_PAGE_NOTICE .
Right to be forgotten

You can now remove all traces of a user when deleting the user from ALM Octane. This facilitates compliance with the GDPR "right to erasure" article.

When deleting the user, you are asked for a reference code. The reference code is used as a placeholder in ALM Octane audit history for the deleted user.

For details on removing all traces of a user, see Delete a user.

For details on configuring the site, see FORGET_USER_ON_DELETE under LOGIN_PAGE_NOTICE .

Back to top

Help Center

We have redesigned the ALM Octane Help Center to make your navigation easier. It now includes the following main categories:

Category Description
Get Started

Start here for a high-level understanding of ALM Octane.

User Help All the information you need to make the most out of ALM Octane's full range of features.
Integrations Explore the many possibilities for integrating your systems with ALM Octane.
Configuration Configure your ALM Octane site and workspaces to meet your organization's needs.
Developer Help Extend ALM Octane's capabilities by developing your own interfacing tools.
Videos Watch a selection of tutorial videos.

Back to top

See also: