SQP Kanban — Three Bugs That Broke Deployment

Thu, 14 May 2026 00:00:00 +0000

Deploying SQP Kanban looked simple on paper. In practice, three bugs made it interesting.

Bug 1 — Mongoose Refuses to Save

Symptom: Adding projects and tasks worked in the UI, but nothing persisted after a page refresh. The save status was stuck on “Saving…” forever.

Two problems hiding as one. First, the save status update in saveBoard() was a bare template literal that didn’t actually call anything:

// This does nothing — it's just a floating string expression
`Saved ${new Date().toLocaleTimeString()}`

Second — and this was the real blocker — the Mongoose schemas for subdocuments (projects, tasks, columns) used the default _id type of ObjectId, but the frontend was generating IDs with crypto.randomUUID(), which produces UUIDs like b14a56c5-2628-4138-990c-cb685fdf04ce. MongoDB ObjectIds are 24-character hex strings. Mongoose threw a CastError on every save attempt.

Mongoose on SQP Dev

SQP Kanban — Three Bugs That Broke Deployment

Bug 1 — Mongoose Refuses to Save