Projects.

Kanban for steady-state work, scrum for time-boxed sprints, or just a list if your team thinks in lists. Switch views without restructuring your data.

Every issue can reference commits in Code, chat threads, docs, design files, emails. Click through from a ticket to the conversation that decided what to build, or to the commit that built it.

Charts computed from your team's actual activity, not story-point fiction. Burndown shows the line, velocity shows the trend, and the overview flags the sprints that drifted and why.

Auto-assign by label, notify the right channel when an issue moves, escalate stale tickets, open a sub-task on every new bug. The rules live in Workflow — visual, editable, no scripts.

The overview scores every open task by urgency — overdue, priority, blocker count, and risk tags — and surfaces the seven that need attention most. You see what's actually blocking the sprint before the standup.

Tasks can depend on other tasks. The dependency view surfaces which open issues are blocked by unfinished predecessors so you can resolve the root cause first, not the symptom.

See how work is distributed across the team — load bars per member, a heatmap across all active contributors, and an alert when anyone is over 90% capacity. Balance the sprint before it tips.

The top-level overview rolls up all active projects by financial exposure — budget times remaining progress. Each project shows its own status donut, throughput bars and upcoming milestones in one glance.