Work operations
Issue log
Track operational issues by severity, status, owner, due date, escalation state, resolution plan, and review queue for a printable issue log.
Sign in to keep templates for reuse.
PreviewPrintable issue log
3 queue rowsIssue log
Launch issue log
Operations team - 2026-05-07 - Facilitator Maya Chen
Issue summary
| Active issues | 3 |
|---|---|
| Overdue | 1 |
| Due soon | 2 |
| Blocked | 1 |
Resolution signals
| Escalated | 2 |
|---|---|
| Critical or high | 2 |
| Missing owners | 0 |
| Resolution queue | 3 |
Issue detail
| Issue | Area | Owner | Opened | Due | Severity | Status | Escalated |
|---|---|---|---|---|---|---|---|
| Checkout failures spike after release | Platform | Noah | 2026-05-01 | 2026-05-06 | Critical | Investigating | No |
| Vendor files arrive late | Vendor | Priya | 2026-05-03 | 2026-05-10 | Medium | Blocked | Yes |
| Support macro needs update | Support | Noah | 2026-05-05 | 2026-05-14 | High | Open | No |
Area summary
| Platform | 1 open - 1 overdue - 1 escalated |
|---|---|
| Support | 1 open - 0 overdue - 0 escalated |
| Vendor | 1 open - 0 overdue - 1 escalated |
Owner workload
| Noah | 2 open - 1 overdue - 0 blocked |
|---|---|
| Priya | 1 open - 0 overdue - 1 blocked |
Resolution queue
- Resolve Checkout failures spike after release with Noah; plan: Patch checkout validation..
- Resolve Vendor files arrive late with Priya; plan: Escalate delivery SLA..
- Resolve Support macro needs update with Noah; plan: -.
Notes
Review overdue and escalated issues first.