Dailerc Workspace

Problem

Our work was spread across several tools: task lists in one place, conversations in another, and it was hard to see what state a piece of work was in, who owned it and which release it belonged to. We wanted work tracking and conversation in one place, inside the admin the team already uses every day, with the same accounts and permissions.

Solution

Each project has its own key, and every work item gets an identifier built from that key and a sequence number. Items have a type (task, bug, feature, improvement, incident), a priority, assignees, labels, start and due dates, an estimate, sub-items, and relations such as blocks, blocked by, relates to and duplicates. States are defined per project and grouped as backlog, unstarted, started, completed and cancelled. Items appear on a drag-and-drop kanban board, in a backlog list, in sprints (planned, active, completed) and in modules with a lead and a target date. Everyone has a "my work" page, and each project has a workload view. Every item has threaded comments with mentions, attachments, and an activity history written through a BullMQ queue. Realtime chat runs on Socket.IO with the Redis adapter and supports direct and group conversations, presence, mentions, file uploads and links between messages and work items.

Results

The Dailerc team uses Workspace to plan and track its own development work, inside the dailerc.com admin. Work items, sprints, modules and the conversations about them live in one place, sharing accounts and permissions with the rest of the admin.

Technologies