Project overview
What a project's front page shows — work by status, recent activity, the active sprint — and how each number is counted.
Every project opens on its Overview: a reading of where the work stands, taken from the record rather than reported by anyone. This page says what is on it and how each number is counted, so that two people looking at it read the same thing. Everyone in the project sees it, Viewers included.
One counting rule
Every number in Rindo that says “done” reads the status category, never the status name. A project’s statuses each belong to one of four categories — triage, todo, in progress, done — and a status in the done category counts as done whatever it is called. That includes the Cancelled status a new project starts with, which sits in the done category: a cancelled task is a finished one to every count on this page, to velocity and to a release’s progress.
Three more rules hold everywhere: a task in the Trash drops out of every live count (a closed sprint’s record is frozen and keeps it); a task with no estimate counts as zero points; an epic’s points are its own, never the sum of its children.
Work by status
Three tiles — To do, In progress, Done — each with the number of tasks in that category. The first two add up the story points they hold; the third says how many were done this week. Above them, one line gives the project’s total — “N tasks · M completed this week” — and adds “· N in triage” when something is waiting to be sorted; triage has no tile of its own.
“This week” is the past seven days, and the count is an approximation: it takes the done tasks that last changed in that window, so an old done task that is edited again re-enters it for a week. The tiles open the task list, unfiltered.
A project without the tasks module — a Library — shows no tiles and no components.
Recent activity
The feed under the tiles is the project’s content record: tasks, documents and test cases created, updated, moved to a status, reverted, imported, moved to the Trash and restored; dependencies added and removed; a pull request merged; drafts proposed, approved and rejected; review passes started and completed; comments, with a line of what was said. The newest eight are shown and Show earlier activity unfolds the rest of the latest two hundred.
Sprints, releases, members and settings are not in this feed. Every event, those included, is on the project’s Audit page, with filters by channel, actor, action and date — open to every member. Audit opens filtered to runner activity; clear that chip to see everything.
The rail
- Active sprint — the sprint’s goal, how many days are left, its dates, and its points “across N tasks”, counting every task in the sprint whatever its status. Without an active sprint the card points you to sprint planning; without the sprints module there is no card.
- Components — each with the number of tasks it holds and how many are done (and in progress, when any are); an empty component shows its description. A component opens the task list filtered to it. Tasks with no component are not on the rail.
Before the work starts
A new project shows a setup checklist instead of the numbers: write the project guidance, connect a Git repository (a Library skips this step), invite members, register a first agent. Each step is ticked from the project’s actual state — a guidance page that has been edited, a connection that exists, a second member who has joined, an agent that was registered — not from a box someone clicked. The Overview takes its normal shape as soon as the first task or piece of activity exists, or once the steps are done; when the last step completes while you watch, the list gives way to a short is set up note, and Reopen setup checklist there brings it back until you leave the page.
The same record elsewhere
- The project card on your home page shows the member count and when the project was last updated.
- My work gathers what is assigned to you and what you watch, across projects, grouped by category.
- Your assistant, connected over MCP, reads the project’s structure with its task counts, the active sprint and the nearest active release, and can read every sprint’s report — see Sprint reports. The Overview page itself has no tool; it is the human view of the same record.