Known and corrected issues
Corrected issues | View the issues in the following table by the default sort order, Corrected in, which shows the corrected issues first. The version number represents the update (Year-Month-Day) in which the issue is fixed. |
|---|---|
Known (open) issues | To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open. |
You can also filter and sort issues according to component or defect ID.
Known and corrected product issues
Component | Description | Status | Found in | Defect ID |
|---|---|---|---|---|
| Alarm policies | While configuring an alarm policy, if you are using the AND and OR conditions together in the selection criteria without using brackets, the resulting alarm events can be incorrectly generated. Resolution Use brackets if you are using the AND and OR conditions together in the selection criteria. | Open | 25.1.02 | DRTOM-42958 |
| Events policies | When you download and modify a CSV file that is uploaded to enrich events by using an advanced enrichment policy, the data in the updated CSV file is not refreshed when you save the policy. This issue occurs intermittently if you click Apply on the Import Settings page before the CSV file has fully uploaded to the advanced enrichment policy. | Fixed in 25.2.00 | 25.1.01 | DRTOM-41991 |
| Events policies | During topology enrichment, if a JWT token expires before BMC Helix Discovery validates the token from the API request, the topology enrichment fails to enrich the event details. | Fixed in 25.2.00 | 25.1.01 | DRTOM-41905 |
Events policies | During the creation or update of an event policy, a problem occurred in the lookup action for advanced enrichment configuration. When you enriched the slot value of a single event out of multiple events, the slot value of another event was also enriched. | Fixed in | 24.4.02 | DRTOM-41589 |
Events | Aggregated events failed to close even after the matching child events were closed. | Fixed in | 24.4.01 | DRTOM-41009 |
Events | While creating a blackout policy by using the REST API, if you added the start and end time in the HH:MM:SS format, the blackout policy was created with an expired state. | Fixed in | 24.3.01 | DRTOM-40897 |
Event policies | Error messages for the If action in advanced enrichment policies are not localized in the Chinese and German locale. | Open | 23.1 | DRTOM-27795 |
Event policies | If the permissions are swapped for two restricted users, a user who has role-based access control to view and manage only blackout policies (core.blackout_policies.view and core.blackout_policies.manage permissions) can view event policies as well. | Open | 22.2.01 | DRTOM-21830 |
| All | The Help icon on the BMC Helix Operations Management user interface opens the documentation for BMC Helix Operations Management version 25.1. Workaround
| Open | 25.2 | DRTOM-42541 |
Related issues
The following links provide information about issues in the integrated BMC Helix products.