Issues tables
Corrected issues | View the issues in the following tables by the default sort order, Corrected in, which shows the corrected issues first. The version number represents the update (Year.Month.Release) or release number (MajorRelease.MinorRelease.ServicePack.Patch) 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 affected version (versions in which the issue exists), component, or defect ID.
Known and corrected issues
| Component | Description | Status | Found in | Defect ID |
| Incident management | When you add a user as a related party to an existing incident, that user receives an email notification to their login ID if the login ID is formatted as an email address and the email address is not updated to their profile. Workaround: Provide the correct email address in the CTM: People profile. | Open | 25.01.00 | DR7O8-1953 |
| Incident requests | When a parent ticket has two child tickets and the service desk agent resolves one child ticket and removes the second child ticket from the parent-child relationship, the parent ticket is automatically incorrectly resolved. | Open | 23.3.04 | DR7O8-1505 |
| Alarm management | For an incident with alarms, when you click on view details, select the secondary alarm with invalid CIs, and click Make primary, the following error messages are displayed: Error (245002) Could not properly update the Incident, so the transaction has been rolled back. Error (45670) Please select a CI from the menu provided or search for a CI by pressing the CI search button. | Fixed in 23.3.02 | 23.3.01 | DR7O8-834 |
| Incident requests | While viewing the alarm details, when you click on the Filter option and scroll down the page to click Apply, the filter grid is not displayed. Workaround: Reduce the screen resolution. | Fixed in 23.3.04 | 23.3.02 | DR7O8-1023 |