Project Management
WB Project Manager
The internal tool WB runs its own delivery on: every request becomes a typed issue with a priority, a live timer and a deadline counted only in working hours, plus a key-based API so other systems file issues themselves.
Some details omitted under NDA
The problem it solved
WB's own pending work lived in notes, chats and scattered documents. Nothing said how long a request had been waiting, and whoever asked never knew whether it had reached the queue.
Worse, the clock ran in calendar days. A request made late on Friday showed up as two days late on Monday, even though nobody works at the weekend.
What the tool does
Workspaces and projects
Work is organised by workspace and by project, each with its own queue.
Typed issues
Every request comes in as a feature, bug, maintenance or improvement, with a priority and a milestone.
Reorder by dragging
Drag to reorder issues, projects and milestones, so today's priority is visible.
A timer on the task
Time is counted live on the issue itself, rather than estimated afterwards.
Deadlines in working hours
The clock only runs Monday to Friday, 09:00 to 18:00. Weekends do not count.
Key-based API
Other systems and automated clients create issues through the API, including several at once.
Its own API documentation
The specification and the documentation page are served by the application itself.
My issues and a dashboard
A view of what is yours and an overview of how the work is moving.
How it turned out
- Every request is an issue with a type, a priority, an owner and a status. Nothing stays only in a conversation.
- The clock that counts is the working-hours clock, so a Friday-afternoon request is not born late on Monday.
- Our own tools and agents file issues through the API instead of pasting text into a chat.
- Honest disclosure: this is an internal single-tenant tool on a SQLite database. It serves our operation very well, and it is not a product we sell as SaaS.
In numbers
4
issue types
9-18
deadline clock hours, Mon to Fri
21
API operations for other systems
For technical visitors
The rest of this page is written for whoever decides the purchase. This block is for whoever has to maintain the tool.
- 13 data models, 24 API route files, 21 documented API paths and 18 test files.
- SLA computed in business hours, Monday to Friday 09:00 to 18:00 with weekends excluded, recalculated on every status change.
- Bearer-key API for external and automated clients, with bulk issue creation.
- OpenAPI specification and a documentation page served by the application itself.
- Login with NextAuth (Prisma adapter) and input validation with Zod.
- SQLite database, which is enough for one internal tenant and deliberately not a multi-tenant SaaS architecture.