Issues tables
Review the following table for issues that were corrected in BMC Helix Operations Management and for known issues that remain open.
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 |
|---|---|---|---|---|
| Events | The advanced filter returns incorrect results if you filter for events from the ALARM class that are present in separate groups. | Fixed in 26.1.01 | 26.1.00 | DRTOM-50223 |
| Blackout policies | A blackout policy is active even after the blackout period ends. | Fixed in 26.1.01 | 25.4.00 | DRTOM-49720 |
| Events | Events are not blacked out even if a blackout policy is active. | Fixed in 26.1.01 | 25.4.00 | DRTOM-50298 |
| Events | On the Events page, the table view that is saved as a preference does not apply when you view the related events of a correlated event. | Fixed in 26.1.01 | 25.4.00 | DRTOM-49824 |
| Event classes | When you export all slots of the ALARM event class, an invalid JSON file is created. | Fixed in 26.1.01 | 25.4.01 | DRTOM-50066 |
| Blackout policies | A blackout policy is executed outside its schedule. | Fixed in 26.1.01 | 25.4.01 | DRTOM-50236 |
| Blackout policies | A blackout policy does not black out events if you use the WITHIN operator in the policy and provide hyphenated values for the WITHIN operator. | Fixed in 26.1 | 25.4.00 | DRTOM-49190 |
| Event policies | You cannot delete an event policy if no configurations are associated with the policy. | Fixed in 26.1 | 25.3.00 | DRTOM-49186 |
| Event policies | If you import an event policy that contains a time frame from one BMC Helix Operations Management server to another, the time frame is not imported. Workaround: Manually associate a time frame with the imported policy. For more information about time frames, see Setting event policy schedules by using time frames. | Open | 25.4.01 | DRTOM-47942 |
| Alarm policies | When configuring an alarm policy, if you use both AND and OR conditions 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 |
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.managepermissions) can view event policies as well. | Open | 22.2.01 | DRTOM-21830 |