GitLab plugin enhancement

The GitLab plugin now supports running automated tests from the test framework. For details, see Functionality supported by CI integrations.

The following auto action enhancements are now available:

• You can now run Deployment Automation application processes via an auto action.
• Auto actions can now run TeamCity jobs.

For details, see Create a release process.

The names of Dashboard favorites are now displayed next to the module name. For details, see Favorites.

You can now access the Dashboard templates from the toolbar. For details, see Dashboard templates.

Export dashboard to HTML

You can now export a dashboard page as an independent html file. This gives you a static version of the dashboard that you can use as a baseline or for auditing purposes. For details, see ALM Octane dashboard.

The following auto action enhancements are now available:

• You can now send emails via an auto action.
• Auto actions can now trigger Bamboo jobs.
• You can now define parameters for a multi-branch Jenkins job. Also, branch name validation for multi-branch jobs has been enabled.
• For GitLab jobs, you can now use the Branch name field to define the CI tags. Unlike with branches, where jobs run on the latest version of code, tags help you run jobs on specific versions, regardless of the commit time.

For details, see Create a release process.

You can now adjust the names of release types to the methodology adopted by your team, by editing the Agile Type list items.

For details, see Set up a release.

Trend widgets enhancement

You can now see run trends for specific backlog items. You can specify Backlog’s last test runs as an item type in the graph’s scope, and filter run item types by Backlog Coverage. For details, see Configure widget data settings.

You can now run a Azure DevOps pipeline with parameters.

For details, see Run Azure DevOps pipelines.

You can now save all visible configurations, such as filters and widgets, as part of your favorite. You can then apply this favorite configuration to additional pipeline runs, without having to set up the filters and widgets again.

For details, see Customize your pipeline display.

The following enhancements to auto actions are now available:

• You can now create auto actions to trigger GitLab jobs and generate document reports. For details, see Create a release process.
• Aborting an ALM Octane's auto action that runs a PulseUno job now aborts the corresponding job in PulseUno, and vice versa. For details, see Run a release process.

The name of the selected favorite is now displayed in the top banner, next to the favorite icon. For details, see Favorites.

You can now inject BDD test results from SpecFlow, using a report generation template file. For details, see Inject BDD test results from SpecFlow.

You can now track and optimize your value delivery process with the following widgets:

• Flow efficiency - waste time across releases: Track the waste time trend across releases. Use the widget AI insights to identify the top work items with the highest waste time in a scope.
• Waste time grouped by waste category across releases: Identify the main causes of waste in each time period. The widget helps you understand whether you've managed to reduce or eliminate any of the waste causes.

For details, see Dashboard widgets: VSM category.

A new widget type allows you to display KPIs as single-number scorecards. For details, see Dashboard widgets: general.

You can now display metrics on the y-axis as an average. For example, in a features summary graph, display the average number of feature story points assigned to each developer. For details, see ALM Octane dashboard.

You can now identify slow phases in features and epics that exceed the phase time threshold set for your workspace. For details, see Analyze release progress and quality.

Risk-based testing analytics now provides insights for recommended tests. The insights help you understand why the tests are recommended. For example, the analytics recommends and prioritizes tests that should provide a good coverage of a selected area and reduce its quality risk. For details, see Quality risk insights.

The Plan Run dialog is now consistent when selecting one or multiple tests. You can set field values for all of the selected tests, including values for user-defined fields. For details, see Plan and run manual and Gherkin tests.