Timesheet & workload

Deckgauge turns issue activity into a CapEx/OpEx time picture — no manual time entry. It infers when someone was actively working from the statuses their items moved through, using rules you control.

deckgauge · Timesheet

July 2026 · Platform normalized

EngineerCapExOpExTop epic

A. Rivera128h22hCheckout v2

S. Chen96h40hSearch relevance

M. Devi140h10hFraud rules

Inferred CapEx/OpEx hours by engineer for a period.

How hours are inferred

When an item sits in an "active work" status, that time is attributed to its assignee and split across the days it was active, capped by a daily maximum. Work on capitalizable initiatives counts as CapEx; everything else is OpEx. No one fills in a timesheet.

Configuring the rules

Active statuses (Settings → Timesheet statuses) — per org tree, choose which statuses mean "actively working" and set the daily cap (e.g. 8h).
In-progress status rules (/timesheet/status-rules) — refine which statuses count per role, with per-person overrides for edge cases.

The views

Timesheet grid (/timesheet) — CapEx/OpEx by engineer and period, per org tree, with a period navigator and normalized vs raw modes.
Report (/timesheet/report) — an aggregated CapEx/OpEx report suitable for finance.
Both are also available as tabs inside an org tree.

Workload

To answer "who's overloaded, who's idle?", use the board's flow and board-health widgets — Work in Progress, Items by Owner, and Stuck in Progress — plus the Developers insight view, which ranks contributors (including AI-assisted PR share) over the last 30 days. See Engineering intelligence.

Retiring a source?Inferred hours depend on items reaching a terminal status. If you stop syncing a board while items are still "in progress", close them out first so they don't keep accruing time.