Timelog
The Timelog is the company-wide view of time logged in KAMI Tasks: every work-log entry, summarised and sliceable. Where a ticket's work log answers "what was spent on this ticket?", the Timelog answers "where did the time go?"
Where: Timelog in the main menu
Choosing a period
Pick a preset period or set a custom range. Everything on the page — summary, tables, export — reads on the range you chose.
What you get
- The summary bar — total hours in the period, plus averages: tickets per person and time per ticket.
- The log table — the entries themselves. Click a column to sort; click an entry for its detail, including the note the person wrote when logging.
- By epic — time folded up by initiative, which turns "we were busy" into "60% of the fortnight went into the migration".
- Export CSV — take the current view into a spreadsheet for billing, capacity planning, or a board pack.
What it is for — and not for
The Timelog is a planning and truth-telling tool: which initiatives actually consume the team, whether the split matches your intentions, what to quote for similar work next time.
It is a blunt instrument for judging people. Hours logged measures hours logged — the person with fewer hours may be the one who forgot to log Friday, and diligent logging is not the same thing as diligent work. Use Sprint Insights for delivery questions; use the Timelog for where-did-the-time-go questions.
Troubleshooting / FAQ
Q: The period shows no data. No work logs exist in that range — the page says so explicitly. Widen the range, or start logging: see Estimates and logging time.
Q: Someone's hours look impossibly low. Almost always under-logging, not under-working. The fix is the habit, not the report.