Role
Designed data structure, category taxonomy & triage workflow
Stack
Ticketing system API integration, generated as a static HTML report
Build method
AI-assisted development (implementation via AI coding tools)

Problem

Security alerts lived scattered across the ticketing system with no aggregate view, so there was no fast way to see volume by source or spot patterns. Getting a pulse on alert volume required manual per-category searches.

Approach

Built a lightweight dashboard pulling ticket data from the ticketing system API into a single filterable table. Category tabs across the top (by alert source) narrow instantly to one system's alerts, while the full table stays sortable by status, priority, and created date.

Kept it intentionally simple: a static, regenerable snapshot rather than live-polling, since the goal was fast triage visibility, not real-time monitoring.

Outcome

Replaced manual per-category searches with a single glanceable view. Category counts up top make volume-by-source obvious immediately.

What I'd improve

Add an alert-aging view and a trend view over time.