Personal statistics

Open and read the statistics

Your statistics are in the Profile tab of account settings. Choose your name at the top of the account menu to open it directly. Account settings opens on Preferences; from there, select Profile, the first tab. The statistics appear under your avatar, name and email. The former /statistics address now opens this tab.

A strip of six figures comes first: Completed, Tasks checked off, Created, Projects, Longest streak and Current streak. It replaces the former all-time totals section. Below it, read the 12-month headline and activity grid, then Where your work went, with breakdowns by project, category and objective, and Work rhythm, with Current workload, Issues per cycle, Due-date gap and Breakdown by effort. Issues per cycle, Due-date gap and Breakdown by effort appear only when they have data. The tab shows its configured periods; it has no date-range filter to select another interval. The surface summarizes your work rather than establishing another member's performance ranking.

Use completed issue counts, pace, active days, streaks and time measurements to inspect your own activity. The activity grid counts issue-completion and notebook-task-completion events, grouped into calendar days in your time zone. The grid never scrolls: it shows the most recent weeks that fit the screen, so a phone shows fewer months than a computer. An active day has at least one such event; the current streak tolerates an empty today but ends at the next empty day. The Completed figure deduplicates issue identifiers: moving the same issue to Done twice still counts once, so an event count and a distinct-issue total answer different questions. The headline above the grid adds the issues and notebook tasks you completed over the last 12 months; point to its number to see the split into issues, tasks and active days. It also counts each issue once over those 12 months: an issue completed again marks each of its days in the grid but adds one issue to the headline.

Time by effort is the median elapsed time from an issue’s first recorded move to in progress until completion, for eligible done issues assigned to you with an effort and both timestamps. It includes elapsed waiting time; it is not a stopwatch of hours worked. The Issue count view shows the underlying sample size. A missing median can reflect no eligible measurements rather than zero duration. Read the unit and the period each section describes before comparing values.

Interpret sparse or changed data

An account that has not yet created or completed an issue, or checked off a notebook task, sees Nothing to measure yet instead of the figures, with a New issue button, or Create the first project when it has no project to create an issue in. An empty period can mean no matching completed work or insufficient activity. It does not prove the account has no issues. Changes in effort labels, scope or work mix can change the comparison without proving you became faster or slower.

Numo can read your statistics through its read-only statistics tools and explain the same numbers. Its access to plan usage or recent executions is also read-only; it cannot change your budget merely by reporting it. For an AI cost problem, open the usage and account settings instead of changing an issue's effort to hide the measurement.

The demonstration account's real history: six completed issues in two projects, thirty created issues, no notebook task checked off.