We are currently using CU5 in our production environment and testing version CU8 on one of our production clusters and CU11 in our test environment.
It seems that in CU11, the User Status algorithm has changed.
We use the User Status to filter our alarms back to our Unacknowledged Alarm tab once an acknowledged alarm has cleared. In CU5/8 and previous versions, once an acknowledged alarm has cleared, the User Status changes from acknowledged, to resolved and then unresolved. It is this last change to unresolved that pushes the alarm back in to our Unacknowledged tab so the change in alarm state can be processed accordingly.
In CU11, however, the User Status seems to revert to resolved only, meaning the alarm does not get sent back to the Unacknowledged tab and operators would therefore be unaware that there has been an alarm change event.
Could someone confirm whether the User Status algorithm was changed in CU11 from previous versions, whether this was reverted in later upgrades, and, if not, what other status change could be used via a filter to have an acknowledged, clearable alarm reappear in the Unacknowledged tab. Just using a Status of Clearable would not be sufficient as it would introduce a number of unwanted alarms.