Workflow
Structured ticket management
High-performance list views designed for scanning and rapid triage. No bloated boards, just fast decision-making.
ZAP-104: Fix authentication middleware latency
ZAP-105: Implement secure file storage
A modern issue tracker built for developers
Manage projects, track bugs, and collaborate without unnecessary complexity. Zap stays fast, readable, and permission-aware from first ticket to final resolution.
zappreview
Product surface
Workflow
Focused, calm, and fast
Active
In Progress
Todo
Role-based permissions
Granular access control for Admins, Members, and Viewers. Secure by design.
Project-based access
Isolate environments and tickets by project. Keep teams focused and data private.
Status tracking
Real-time ticket updates and audit history for every issue lifecycle.
Secure attachments
Permission-aware file handling that keeps uploads tied to the right tickets.
Clarity in every view.
Designed for functional engineering over visual clutter, with the same server-first access model that powers the rest of the product.
Dashboard View
Analytics Dashboard
Get a bird's-eye view of team velocity, project health, and ticket distribution without losing the detail needed to act.
Contextual Detail View
Everything needed to resolve an issue lives in one focused workspace: description, comments, assignments, and attachments, separated by tonal depth instead of noise.
Detail View
The Stack
Built with performance and scalability in mind.
ASP.NET Core
PostgreSQL
TS
TypeScript
Remix SSR
RBAC Auth
REST API
Why I Built This
Zap is a portfolio project inspired by tools like Jira and Linear. I built it to demonstrate real-world backend architecture, server-enforced authorization, and full-stack product thinking beyond a surface-level UI clone.
The focus is practical engineering: relational data modeling, secure file handling, granular permissions, and a developer-first interface that still feels premium.
System Design & Full-Stack Implementation