What's new (SaaS)
The following new features and enhancements are introduced in ALM Octane version 12.60.21.
On-premises: If you are using the 12.60 CP8 On Premises version, you can see the full list of new features in your version here: What's new (On Premises).
What's new video
Watch the What's new video:
The following enhancements have been introduced for on-premises installations:
SSO authentication is now supported.
For details, see:
ALM Octane retains the last time each user logged in. The log in times can be seen in the Settings area for the site.
Including an internalALM Octane user migrates the user as an LDAP user.
Data access control
The following data access controls have been implemented:
Control who can access defects
Control which defects users can access, based on their role and access categories.
For details, see Set up data access.
Restrict access to vulnerability data
You can now define permissions on vulnerability data, based on your security needs. Within Settings > Spaces > Permissions, you can specify which users can view data regarding vulnerabilities, or edit vulnerability status. For details, see Assign roles and permissions.
Integrations and Synchronization
The following enhancements are now available:
We created an integration mechanism that enables you to select automated tests in any testing framework, and run them in the context of your ALM Octane test suite. For details, see Trigger automated test runs in your testing framework (technical preview).
ALM Octane can now discover and run UFT tests via Bamboo, in addition to via Jenkins. The integration enables ALM Octane to reflect the UFT tests from your SCM repository as executable automated tests. For details, see Set up UFT integration.
To help you bring security testing into your development cycle, ALM Octane now integrates with on-premises Fortify Software Security Center, in addition to cloud-based Fortify on Demand. For details, see Set up an integration with Fortify.
When you move a Jira issue from one synchronized Jira project to another, this move is reflected in the corresponding ALM Octane defect. For details, see Mapping multiple JIRA projects.
The following agile enhancements are now available:
We've added a planning board to help you plan the content of your releases, balance work load between teams, and identify problematic dependencies between features.
For details, see Use the planning board.
Dependencies between backlog items
You can now define dependencies between features, user stories, and defects. Dependencies are indicated on the planning board to help you decide which features can be added to scope.
For details, see Create dependencies.
The following quality enhancements are now available:
Rules and UDFs for manual runs and suite runs
Admins can now create rules and UDFs for manual runs and suite runs.
Rules: The rules can perform the following actions: Make required, Send email, and Trigger webhooks.
UDFs can now be selected when customizing fields in the Run or Plan test suite dialog boxes.
The values of the UDFs in a test suite can be assigned automatically to its corresponding test runs, as determined by the value of the new COPY_RUN_SUITE_UDFS_TO_RUNS configuration parameter.
Until now, you could create a parameters table in manual tests, enabling you to run the test in iterations, using a different set of values each time. In this release, we've added the ability to create multiple data sets for the data table, enabling you to select the data set relevant to the scenario you are testing.
For details, see Use parameters in tests.
A new space-level parameter, MAX_TREE_DEPTH_APPLICATION_MODULE, now allows you to customize the number of levels your application module tree can have.
For details, see Set configuration parameters.
You can now filter items that you are following or items that are listed in your My Work module using the Followed by me and Assigned to me filters.
Test run history graphs
You can now create custom graphs that display manual test run history.
Note: The Test Runs item type has been changed to Last Test Runs.
Use Last Test Runs to see only the latest runs per release and environment. This is useful for coverage and release status reports.
Use Test run history (manual) to report on all runs, not only the latest ones. This is useful when you want to track effort and each run is significant.
You'll notice changes to the toolbar:
- We've added labels to the buttons.
- Inactive buttons are now hidden.
- We've moved less common actions to the More drop-down list.
- The right-click context menu is now aligned with the toolbar.
The following administration and customization enhancements are now available.
Until now, time-related calculations, such as velocity and release burn down, did not reflect non-work days. In this release, we've added the ability to define work days on a workspace or team level. Work days are reflected throughout the system, wherever time-related calculations are made.
For example, the velocity curve in a graph now reflects non-work days. Instead of being straight, the curve is now jagged, with the non-work days displayed as plateaus.
For details, see Define work days.
You can now add values to the Severity and Priority system lists.
These enhancements are now available:
In the previous release we introduced the ability to associate commits with backlog items manually, linking from a commit to a backlog item. In this release, you can also link from a backlog item to a commit.
For details, see Associate commits with backlog items.
The following enhancements are now available in the Help Center:
Best practices have been incorporated into the installation information in this Help Center. Best practices are available for: Deployment, Backups, Maintenance, Setting up spaces and workspaces.
Note: Note: The Maintenance best practices were previously provided in a separate PDF guide, which is now discontinued.
For more details,
Troubleshooting Gherkin test automation
We've added a section on Gherkin test automation troubleshooting.
For details, see Troubleshooting .
For a list of REST API changes, see What's changed in the REST API.