Your first project
Create a project, file work, move it across the board, sort what comes in, and plan a sprint.
A project is the unit of everything in Rindo: its members, its rules, its record. This page walks through the first week — creating one, the task record, the board and its workflow, the Triage queue, and sprints.
Create a project
Choose New project, give it a name, and Rindo suggests a key from it. The key is what every task number starts with (ACME-12), so choose it once: it is unique on the whole instance and cannot be changed later. Letters and digits only, starting with a letter; at least three characters on app.rindo.io.
A project starts from a template that decides its modules — tasks, sprints, releases, test cases, chat and sources — and that cannot be changed later: a module that is off has no tab. Set the project’s timezone too: it decides where a day begins for the burndown.
On the Free plan an account owns one active project; archiving frees the slot.
Tasks
A task carries a title and a description, an assignee, a priority, and the status it sits in. The number is per project and never reused, even after a delete. Beyond that:
- A task can be an epic that groups others, or a subtask under a parent. An epic carries its own estimate; there is no rollup from its children.
- Dependencies — blocks, blocked by, related — link tasks; a chain that would loop is refused, and a blocked task shows it.
- Components (Frontend, Backend, Mobile…) and custom fields you define per project — text, number, date, select, checkbox, URL, user — sit on tasks, pages and test cases alike.
- Story points on the modified Fibonacci scale (0, 1, 2, 3, 5, 8, 13, 20, 40, 100).
Every change to a task is recorded on the project’s audit trail, with who made it and through which channel.
The board and the workflow
The board’s columns are the project’s statuses, except the triage ones, which live in the Triage queue. Each status belongs to one of four categories — triage, todo, in progress, done — and the category is what gives it its colour and what the counts, velocity and readiness read. A new project starts with New (triage), Todo, In Progress, In Review, Done and Cancelled, and any status may move to any other.
Strictness is something a team opts into: in Settings → Workflow you add or rename statuses, and you tick the transitions that are allowed. From then on a move that is not allowed is refused — on the board, and for an assistant or agent over MCP just the same, which can read the workflow before it acts. Creating a task may target any status; the rule is about moving existing ones. A status that still holds tasks cannot be deleted until they are moved.
Triage
Triage is where things that were logged but not yet decided wait: a question, a request, an impediment, a task a project agent filed on its own. Nobody has confirmed they are work. From the Triage queue you confirm an item into a todo status, cancel it, or discuss it. Items in triage never count as working items and never enter a backlog.
A task a project agent files without a status lands in Triage — a project setting, on by default, when the workflow has a triage status. What your own assistant files as you lands where yours do.
Sprints
A sprint is a time-boxed iteration with a name, a goal and dates; a project has at most one active sprint at a time. The product backlog is every working item (todo or in progress) that belongs to no sprint; planning is dragging items from it into the sprint. The sprint board is the board filtered to the active sprint. When you close a sprint, what is not done moves back to the backlog or into the next one — your choice.
Velocity is the rolling average of the last five sprints, counting what reached a done status; the burndown takes a daily snapshot in the project’s timezone, with scope changes and an ideal line.
Your assistant in the project
Connect your assistant and it works in the project as you: it can read the workflow and the fields before it acts, files tasks where you would, and its edits to a task’s description wait for approval when the project asks for it — see Review what your AI proposes.
Keep up
Watch a task — commenting on a page watches it too — and its changes reach your Inbox. My work gathers what is assigned to you and what you watch, across your projects.