Estimates, time and reports

Read progress in the right unit and distinguish estimates, time logs and completion.

Choose points or hours

Each board chooses story points or hours. Tickets preserve separate points, original hours and remaining hours. Switching a board changes its displayed planning unit without calculating a conversion or replacing other estimates. Sprint history retains the unit recorded for that sprint.

Story points express relative estimated effort. Original hours record an estimate; remaining hours record work left. Logged hours record work actually performed. These values answer different questions and must not be added together as one measure.

Log and correct time

Open a ticket's Time tab. Add a dated log with hours and notes, then save. Logging time does not automatically decrement remaining hours; adjust the remaining estimate deliberately when needed.

Members edit their own logs. Managers can correct another person's log with the required reason and audit history. Use notes to explain the work, not credentials or sensitive customer data.

For Harbor support, a ticket might have 6 original hours, 2 remaining hours and 5 logged hours. That means the current estimate exceeds the original plan; it is not an arithmetic error that the values differ.

Scrum reports

• Burndown: use the sprint baseline, remaining work and recorded scope changes. Added work can raise the line; a scope reduction is different from completion.
• Velocity: compare completed sprint totals in the same recorded unit. Do not combine hours-based sprints with points-based sprints.
• Scope changes: inspect additions/removals and their dates when explaining why a sprint ended differently from its starting plan.

A Done category supplies completion meaning; a named stage such as In review does not count as Done unless its workflow category says so.

Kanban reports

Throughput counts completed work; cycle time describes elapsed flow through work; aging highlights work still open. Inspect WIP warnings alongside aging tickets to find queues and blockers rather than interpreting every old ticket as active effort.

Reports respect project access. A shared board can show different permitted totals to different viewers. Query/report aggregation can cover the complete matching set even when a board or ticket widget displays only a bounded subset.

Hours and dashboard measures

Compare planned original hours with logged hours, then inspect remaining hours separately. Dashboard numeric measures include ticket count, points, original hours and remaining hours. Labels identify their units; pie charts count tickets rather than mixing estimate totals.

If a chart looks surprising, check its source query, period, grouping, estimation unit and current access before changing estimates. See dashboard configuration for sources and drill-through.