Projects

Projects group related tasks under a shared theme. They are flat by design: no hierarchy, no dependencies, no subtasks. A task belongs to at most one project.

This page covers the concept. For the mechanics of creating, assigning, renaming, archiving, and deleting, see working with projects.

What a project is

A project is a named container for tasks that belong together: a client, a launch, a trip, a side build. It is a convenience for grouping and focus, not a plan with structure. If a project starts to feel like it needs subtasks, that is usually a sign it is really several projects, or several plain tasks.

How tasks join a project

The fastest way is while capturing: type # and the project name, like #Website, and Rymi matches it (or offers to create it). You can also assign a selected task with the P key, or from its row. See smart parsing.

The project view

Open a project and its tasks are grouped by section, with Inbox, Today, and Backlog headers and live counts. A task assigned to a project still lives in your normal sections too. The project view is simply a focused lens on everything under that theme.

Shared projects

With Rymi Together, a project can be shared with another person. Shared projects add an Unassigned pool and per-task assignment, so a small group can divide work without turning Rymi into a team tool. See sharing a project and members and assignment.

Rymi deliberately stops at shared projects. There are no team workspaces; collaboration happens around a shared project, not an organisational hierarchy.