| Issue | First reported in | Description |
|---|---|---|
| 5038440 | 3.1.3.29 | In the Incident monitoring task, the On hold group is collapsed by default when incidents are grouped by state. |
| 5033606 | 3.1.3.24 | Incident notifications may be processed out of sequence if they arrive before Security Desk initialization completes. |
| 5032212 | 3.2.1.15 | In Security Desk, the comment box in a dynamic user procedure step displays the same text that was added in a previous step or incident. |
| 5032050 | 3.2.1.15 | In the Incident monitoring task, profile filters hide new incidents that are not linked to the user’s profile, even if the user is the sole recipient. |
| 5027567 | 3.2.1.6 | .NET color rendering functionality causes a memory leak in Security Desk and Config Tool, which eventually crashes both applications. |
| 5013625 | 3.2.1.0 | In the Incident monitoring task, if an entity on the map is not attached to any area, the map is not displayed when an incident is triggered on that entity. |
| 4999064 | 3.2.1.8 | The Incident Manager does not recover from RabbitMQ query or command connection failures due to a missing step required to rebuild those connections. |
For installation prerequisites and setup, see the Installing Mission Control section in the Deployment Guide.