Overview¶
The Overview page is the operational starting point. It answers: what needs attention right now?
Metrics¶
The top metrics summarize current active SLA pressure:
- active eligible issues
- issues at risk soon
- breached issues
- paused issues
Excluded issues are not treated as active SLA work.
Needs attention¶
The Needs attention right now list is focused on non-terminal issues that are:
- breached
- running
- paused
Terminal issues are excluded from this operational attention list.
The list is sorted by the next relevant target so the nearest deadline appears first.
Example: why a running issue appears¶
A running issue appears when it is still open in an SLA measurement and has not reached a terminal state.
Example:
| Field | Value |
|---|---|
| Issue status | In Progress |
| Resolution SLA | RUNNING |
| Next target | May 14 23:59 |
This issue should appear because it still needs operational attention before the target.
Example: why a closed issue should not appear¶
If the latest issue status is terminal, such as Closed or Done, it should not appear in Needs attention right now, even if it breached earlier.
It may still appear in Reports because Reports measure historical performance.
Deadline logic¶
For deadline-mode issues, the next target is the deadline target.
For response/resolution issues, the next target is:
- response target if response is still running
- resolution target if response is complete and resolution is still running
- the relevant completed target for fallback display
Expanding issues¶
You can expand an issue from Overview to inspect the same explanation panel used on the Issues page.
Use this when an issue appears in the attention list and you need to understand why it is running, paused, or breached.
Common checks¶
If Overview seems empty but Reports show running issues:
- confirm the issues are not terminal
- confirm they are not excluded
- check active filters and project configuration
- inspect issue detail for missing Start or terminal mapping
If Overview shows an issue that looks finished:
- confirm the latest source status maps to
Terminal - check whether the source issue status is one of the terminal statuses recognized by the project
- open issue detail and inspect the final event in event history