The following issues were resolved in the ALM Octane 24.1 release:
|There was an unhandled exception when changing the field order in a list.
|Unstable behavior occurred in the REST API when using api_accesses with the expiration and is_valid properties.
|An exception was thrown when clicking Favorites.
|The terms swimlane, swim lane, and lane were not used consistently in the user interface.
|When locating an application module via a search, its Details tab did not open.
|The title and message in the Admin Role Required warning popup, indicated Shared even when the space was isolated.
|Long response times were encountered for PUT run_steps requests.
|Dashboard popup details were missing after an upgrade.
|The trace from filter did not show correct results.
|It was not possible to edit a Make Required business rule that used similar fields in different workspaces.
|When a user assigned a calendar to a team with an Alert User business rule, no alert was displayed and the user could not proceed.
|The popup window that opens when accessing Call to test steps had an incorrect behavior.
|Users could not log in to the ALM QoT offline client with SSO.
|When modifying certain fields in the Team entity, an error occurred.
|The Covering tests field in features was not refreshing automatically.
|The Content field in Gherkin Auto Runs (GARs) did not show the correct number.
|When trying to deprecate a list item, a List could not be saved error occurred.
|The configuration parameter list in the online help did not match the list shown in the product.
|Users were unable to access linked entities within external actions.
|Rank order was not observed in exported backlog Excel files.
|When restoring a BDD scenario item, a BDD scenario with a new ID was created.
|The example Excel import file incorrectly showed a semicolon as a separator, instead of a comma.
|An error occurred when deleting deployments.
|ALM Octane was not sending webhooks.
|Enums were not available in the interactive API client.
|When exporting BDD Scenario (BSC) entities, an attachment description error was displayed.
|The Feature coverage widget was not available.
|AI analytics scope was mistakenly set to Include all workspaces by default, instead of Exclude all workspaces.
|For big xUnit files, Jenkins test results were not imported into ALM Octane.
|In the Generate Document Report window, the Apply and Cancel buttons were off screen and not accessible.
|In the Jenkins plugin, discovery jobs were failing.
|Decimal values were omitted when importing tasks from an Excel file.
|Users were unable to access test steps.
|When trying to create new defects, the Must have a valid phase message was displayed.