🛠️ Maintenance

Definition

A Maintenance item (an Issue) is a bug or operational problem you track to manage the run. It can be categorized by type — Bug, Security, Performance, Reliability, Technical debt, Dependency, Infrastructure as code, Observability, Operational task, Compliance & governance, or Won't fix — and it moves through a simple status lifecycle: Open → In Progress → Closed.

Budget allocation

Activities related to maintenance items are mapped to an OPEX (operating expenditure) budget — they keep the existing run going. This is the counterpart of PRDs, whose delivery work is mapped to a CAPEX (capital expenditure) budget as it builds new assets.

How to use it effectively

• Give it a clear, specific title so it's easy to scan in the list
• Pick the right type and keep the status up to date as work progresses
• Set the started and closed dates to keep an accurate timeline
• Link it to the related PRD, Workload, or Service Incident for end-to-end traceability
• Use the description to capture context, reproduction steps, or remediation notes

Get an overview of maintenance items

The maintenance view lists all items with search, filtering, grouping, and a colored status chip at a glance. Columns surface the type, status, started/closed dates, and linked PRD and Workload, so you can track what's open and what's been resolved.

Create a maintenance item

Use the Create button to open the form. Set the title, type, and status, optionally add the started and closed dates, and link it to a PRD, Workload, or Service Incident. Save to start tracking it.

Document a maintenance item

Open an item to follow up. On the Description tab, use the block editor to document context, repro steps, and remediation. The Metadata tab shows the type, status, dates, linked aggregates, and author at a glance.