resolution-tracker
Track issue resolution status across the full [issue lifecycle](references/issue_lifecycle.md), measure time-to-resolve against [SLA targets](references/sla_targets.md), and surface patterns across resolved issues — all from vault markdown issue records, without an external ticketing system.
Inputs
- issue_id — Issue ID to update (e.g. ISS-2026-04-05-login-failure)
- new_status — Target status: open | investigating | resolved | verified | closed
- action_taken — What was done — used as the resolution log entry
- resolved_by — Name of the person who resolved or advanced the issue
- scope — Client ID (e.g. acme) or 'all' for portfolio-wide report
- period — Date range for the report (e.g. 2026-Q1, last-30-days). Defaults to all-time open issues.
- scope — Client ID or 'all' for portfolio-wide analysis
- period — Date range to analyse (e.g. last-90-days, 2026-Q1). Defaults to last 90 days.
How you ask
- open issues
- resolution SLA
- issue retrospective
- service quality report
- resolution methodology
Outputs
- issue-report (markdown)
- trend-report (markdown)
- updated-issue-note (markdown)
Levelbeginner
Inputconversation
Outputdocument
Setup[none]
Roles[Operations Manager]