You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: When escalating an aggregation there is no way to tie a specific alert to an escalation short of using the open and close time stamps. When going back to review a closed escalation it's difficult to see exactly what alerts were investigated.
Solution: When acknowledging or escalating alerts a new field is inserted with an acknowledge/escalated status into the record (from what I'm seeing). Inserting the case ID into the acknowledgement would be fairly simple to add at that point. Please insert a case ID into the alert when escalating so it's possible to tie individual alerts to a case. This also would also simplify the aggregation query in cases. The aggregation query could simply be to look for the case ID.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem: When escalating an aggregation there is no way to tie a specific alert to an escalation short of using the open and close time stamps. When going back to review a closed escalation it's difficult to see exactly what alerts were investigated.
Solution: When acknowledging or escalating alerts a new field is inserted with an acknowledge/escalated status into the record (from what I'm seeing). Inserting the case ID into the acknowledgement would be fairly simple to add at that point. Please insert a case ID into the alert when escalating so it's possible to tie individual alerts to a case. This also would also simplify the aggregation query in cases. The aggregation query could simply be to look for the case ID.
Beta Was this translation helpful? Give feedback.
All reactions