What needs attention now?
Group incidents by priority and state, then open the underlying cases before changing assignments.
Review response, request, change and service evidence from recorded fields.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Open | 26 | ||
| Acknowledged | 6 | 23% | |
| Investigating | 2 | 33% | |
| Resolved | 1 | 50% |
Sample counts per stage
Group incidents by priority and state, then open the underlying cases before changing assignments.
Compare acknowledgement and resolution times on incidents and due and completion dates on requests.
Read advisory decisions against changes, then inspect deployment outcomes for the affected service.
Use verified service-asset links and check them against the register.
Group integration events by source and outcome, then inspect the rejected entries.
Count incidents by Priority and Status for the current response queue.
Compare opened at with acknowledged at and resolved at on incidents.
Compare due at and completed at across service request statuses.
Group CAB approvals decisions by their Changes and Services.
Show Assets connected to each Service through service asset links.
Compare started at and restored at for each service outages entry.
Group knowledge articles by Status, Service and Owner.
Group integration events by source system and Status.
Start free, then use Proto to change fields, steps and approvals before your team goes live.