Technical Debt Item Block
Document and track technical debt with impact, effort, priority, and resolution status.
The Technical Debt Item block provides a structured way to document and track technical debt across your codebase. It captures the impact, effort to resolve, priority, and current status, enabling informed decisions about when and how to address accumulated debt.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Title | Yes | Brief description of the debt item |
| Description | No | Detailed explanation of the issue and its implications |
| Impact | No | Business or technical impact (High, Medium, Low) |
| Effort | No | Effort to resolve (High, Medium, Low) |
| Priority | No | Resolution priority (Critical, High, Medium, Low) |
| Category | No | Type of debt (Code Quality, Architecture, Testing, etc.) |
| Owner | No | Person or team responsible |
| Target Date | No | Planned resolution timeframe |
| Status | No | Current status (Identified, Planned, In Progress, Resolved) |
| Notes | No | Additional context or remediation ideas |
Priority Levels
Example: Legacy Authentication Module
A critical debt item requiring architectural changes.
Example: Test Coverage Gap
A medium-priority testing debt item.
Example: Dependency Updates
A low-effort maintenance debt item.