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 You need: access to the projects whose time you are viewing
When to use this, and when not to
| The question | Use |
|---|---|
| Where is the team's time actually going? | Timelog |
| How much is left on this ticket? | The ticket, or My Work |
| Did we deliver the sprint? | Sprint Insights |
| How hard is someone working? | Nothing here — see below |
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 written 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. By epic is the view that most often changes a decision.
It is a blunt instrument for judging people. Hours logged measures hours logged — the person with fewer may be the one who forgot Friday, and diligent logging is not diligent work. Worse, using it that way changes behaviour: people log to look busy rather than to record what happened, and the data stops being usable for the planning questions it is good at.
Use Sprint Insights for delivery questions, and the Timelog for where-did-the-time-go questions.
What Happens Next
- The Timelog reflects work logs as they are entered — it is a read of the same data the tickets hold.
- Exports are a snapshot; re-export after corrections rather than editing the file.
- Time logged against a ticket also counts toward its sprint's hours figure in Insights.
Tips
- Read it by epic first, by person last. The initiative view answers the questions worth asking.
- Check it before quoting similar work. "How long did the last migration take?" has an actual answer here.
- Expect under-logging, and plan around it. Most teams log 60–80% of real time. Comparing periods works; comparing to a 40-hour week does not.
- If the data is poor, fix the habit, not the report. Logging as you go is a two-minute discipline; reconstructing a fortnight is an hour of fiction.
Troubleshooting / FAQ
Q: The period shows no data. No work logs exist in that range. Widen the range, or start logging — see Estimates and logging time.
Q: The totals look far too low. Under-logging, almost always. The fix is the habit.
Q: I cannot see another team's time. The Timelog respects project access. You see the projects your groups reach.