Track and Resolve Project Issues Efficiently

This skill designs comprehensive issue log systems that capture, categorize, track, and resolve problems throughout a project lifecycle. Core principles: structured classification (Bug/Enhancement/Task/Story/Epic type, Critical/High/Medium/Low priority, Blocker/Major/Minor/Trivial severity, aligned to business impact), defined lifecycle states (New, In Progress, Testing, Resolved, Closed, Reopened) with clear transition criteria and ownership, bidirectional traceability between issues, requirements, test cases, and deliverables, and actionable documentation detailed enough for reproduction and diagnosis without follow-up questions.

Use it when a project needs a standardized issue log template and priority matrix instead of ad-hoc bug notes with inconsistent fields.

### Issue Header
- **ID**: PROJ-001
- **Title**: [Component] Brief descriptive title
- **Type**: Bug/Enhancement/Task/Story/Epic
- **Priority**: Critical/High/Medium/Low
- **Severity**: Blocker/Major/Minor/Trivial
- **Status**: New/In Progress/Testing/Resolved/Closed
- **Reporter**: Name/Role
- **Assignee**: Name/Role

Each issue entry carries a Description block (Summary, Environment, numbered Steps to Reproduce, Expected vs Actual Result, Workaround), a Technical Details block (Component/Module, Version, Dependencies, Logs/Error Messages), and a Resolution block (Root Cause, Solution, Test Results, Code Changes). The priority matrix maps concrete scenarios to each level - Critical covers system-down, data loss, security vulnerabilities, and production outages; High covers major feature failure, significant performance degradation, compliance violations, and customer-facing issues; Medium covers minor feature issues and documentation gaps; Low covers nice-to-have improvements. Advanced tracking defines SLA targets in JSON (time-to-first-response under 4 hours, resolution time from 24 hours for critical down to 1 month for low, resolution rate above 95%, satisfaction above 4.5/5) plus automation triggers for overdue notifications, age-based priority escalation, and weekly status reminders. A monthly report template rolls up volume metrics (new/resolved/net change/backlog), performance metrics (average resolution time, SLA compliance, satisfaction), trend analysis, and action items.

JIRA integration is shown as a custom-field configuration block adding businessImpact (Revenue Impact/Customer Experience/Operational/Compliance), effortEstimate in hours, and rootCauseCategory (Code Defect/Configuration/Environment/Process/External) as selectable fields, so root-cause trends become queryable rather than buried in free text.

Project managers and QA leads who need a consistent issue log structure, priority/severity matrix, and SLA-driven reporting across a project - not a bug tracker used with whatever fields each reporter happens to fill in. Workflow guidance closes the loop: run daily or weekly triage meetings against standardized priority criteria, define escalation paths with notification chains and response-time requirements for critical issues, maintain real-time status with timestamped transitions, keep categorization taxonomies consistent so trend analysis stays meaningful across categories, and review closed issues regularly to convert recurring problems into preventive process changes.