What's new in 15.1.90

The following new features and enhancements are introduced in the ALM Octane 15.1.90 release.

In this topic:

What's New video

My Work

The My Work area has been fully redesigned. It now provides you with the full array of ALM Octane capabilities. My Work now uses the standard ALM Octane grid view, enabling you to perform regular actions such as filtering, grouping, sorting, adding columns, and bulk updates.

The new view is enabled by default. You can use a toggle to switch to the old view if needed.

For details, see My Work area.

Back to top

Backlog and Requirements

The following backlog enhancements are now available:

Enhancement	Details
Features timeline	Track your feature progress with new feature timelines. A new Grid Timeline view in the Features tab displays color-coded bars for each feature, illustrating the feature's progress over the release timeline. Each feature is represented by a colored bar indicating its current phase. The bars are positioned according to the feature's start time and target milestone. For details, see View the feature timeline.
Defects recycle bin	Defects that you delete are now placed in a recycle bin. You can restore defects from the recycle bin to the workspace. For details, see Restore or delete defects from the recycle bin.
Requirement description versions	You can now save changes to requirement descriptions as a version, and then compare changes between versions. For details, see Requirement management.
Import tasks	You can now import tasks from an Excel file. For details, see Import from file.

Back to top

Quality

The following quality enhancements are available:

Enhancement	Details
Quality risk analysis	ALM Octane now includes quality risk insights that indicate which areas in your product are at high risk and may require further testing. Application modules are assigned quality risk scores that allow you to identify the problematic areas. For details, see Quality risk analytics.
Test coverage for a specific work item	For manual and automated runs, you can customize test runs to cover specific work items, such as epics, features, and defects. For details, see Test specific backlog items.
Copy tests across workspaces	You can now copy manual and Gherkin tests from one workspace to another. For details, see Copy or move items to another workspace.
Manual runner timer	You can now measure the duration of manual or Gherkin test runs automatically. The timer starts when the Manual Runner window is launched, and stops when the Manual Runner window is closed. For details, see Test Execution.
Test suite history	The History tab for test suites now includes logs on reordering tests in a test suite. This is in addition to the logs on adding and removing tests in the test suite.
Link to custom run reports	If you use custom test run reports, you can now define a URL pattern in your job configuration or test runner, pointing to the report location. Automated test run results in ALM Octane will include a link to the custom report as defined by the URL pattern. For details, see the step "Test Run Reports" in Configure steps: Define test and test run information.
Environment value passed to test runner	In the test execution framework, the environment value is now passed to the test runner job for multiple automated runs with the same environment.

Back to top

Pipelines

The following pipeline enhancements are available:

Area	Enhancement
SCM Branches	If you configure ALM Octane to link to your Source Control Management (SCM) system, the Branches tab now shows the branches associated with features, stories, and defects. You can also see details about each branch such as its SCM user, when it was created and updated, and whether it has commits or pull requests. For details, see Track branches in your SCM system. A new external action, Create Branch, enables you to create a branch in your SCM repository from within an ALM Octane entity. This enables you (for example) to create a feature in ALM Octane, and then select the Create Branch menu command to create a branch in your repository for this feature. You can use the SCM Change Pattern settings to name the branch using your branch naming template. The following SCM systems are currently supported: Bitbucket Server, Bitbucket Cloud, and Github Cloud. For details, see ALM Octane Create Branch External Action.
Run automated tests on any host	If you don't have a dedicated CI server, and you only need a lightweight CI to be used primarily for triggering UFT One test runs from ALM Octane, refer to the new Minimal Jenkins Installation for ALM Octane quick start guide.

Back to top

Dashboard

A new powerful widget reflects relationships between a selected primary entity and a secondary entity. For example, you can see all of your team’s features and the defects that cover them.

For details and more examples, see Traceability graphs.

Back to top

Release processes

The following enhancements are now available in release processes:

Area	Enhancement
Query criteria	In addition to user-input criteria, you can now define query criteria in quality gates. You define a rule that checks whether the number of items within a given scope meets a specified condition. ALM Octane automatically evaluates the criterion, and passes or fails the criterion accordingly. For details, see Define quality gates.
Dashboard widgets	You can create dashboard summary widgets based on processes. You can filter and group the processes based on attributes of the current stage (cross filtering and cross grouping). For example, show all active processes with CurrentStage.Type = 'Testing'. You can also cross filter the release processes grid based on attributes of the current stage.

Back to top

Back to top

Back to top

Attachments

The following changes and enhancements now apply to attachments:

• You can now paste images into comments. The images are saved as attachments of the item. For example, if you paste an image in a defect's comment, the image is added to the defect's attachments. For details, see Attachments.

• In the past, images that you embedded in memo fields via REST API were saved to the database as base64 strings, as part of the memo field entries. You could embed any number of images to any memo field.

  Now, images that you embed in memo fields via REST API are handled the same way as images pasted in the UI: The images are converted to image files. The files are saved in the file repository and referenced from the selected memo field.

  The same rules that govern uploading attachments via the UI now apply to images posted via REST API.

  For details, see Embedded images.

Back to top

Supported platforms

Following are changes to supported platforms:

• ALM Octane 15.1.90 supports Elasticsearch version 7.9.1. If you are using an earlier version of Elasticsearch, you must upgrade to 7.9.1. For details on supported platforms, see Support matrix.
• ALM Octane now integrates with the PulseUno CI. For details on supported functionality, see Functionality supported by CI integrations. For details on configuring PulseUno, see Integrate with external request providers.

Back to top

See also:

• What's New in ALM Octane - earlier versions
• Readme
• Support matrix