> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ruber.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

> The board and its seven states, priorities, due dates typed in words, notes that hold a document, and turning a mail thread into a task.

## The board

Seven states, in order:

`To do` · `In progress` · `In review` · `QA` · `Done` · `Cancelled` · `Hold`

Review and QA are separate because they are usually different people doing
different work. **Hold is not Cancelled** — one is waiting on something, the
other is over — and collapsing them loses the only distinction that matters when
you come back in a fortnight and ask why nothing moved.

Drag a card between columns to change its state. Order within a column is
yours; dropping a card between two others writes a single number rather than
renumbering the column, so two people rearranging at once do not fight.

## Priority

Five levels — none, low, medium, high, urgent — stored underneath as 0–9. The
wider range is there so a value that arrives from an import or a script keeps
its ordering instead of collapsing into five buckets on the way in.

## Due dates

Type them. The field takes ordinary language:

```
next friday
eow
in 3 weeks
sept 15
3d
24h
```

A grammar reads this, not a list of formats, which matters because the useful
inputs are exactly the irregular ones nobody thinks to add to a list.

A list groups into **Overdue**, **Today**, **Tomorrow**, **Upcoming**,
**Someday** and **Completed**. Someday is a real bucket rather than a polite
word for forgotten: a task with no date still has somewhere to be.

## Notes

A task's notes are a document, not a text box. Type `/` for:

* headings
* bulleted and numbered lists
* checklists
* quotes
* dividers
* images
* code blocks with syntax highlighting

Useful when the task *is* the write-up — a bug with a stack trace, a decision
with its reasoning.

## People and history

Assign a task to anyone in your organisation. The card carries comments and a
record of what changed, and that record is written by the app rather than typed
by whoever remembered to.

## From mail, and to the calendar

Turn a thread into a task without leaving it. The task keeps the link, so "what
was this about" is one click rather than a search.

A task can also point at a calendar event, so the thing to do and the time set
aside to do it stay one item instead of two that drift apart.

## Settings

Sort order, whether completed tasks stay visible, whether deleting asks first,
whether a new task offers to create an event, and how far ahead a reminder
fires. Set once; every device follows.

## What tasks do not do

**No recurring tasks.** A task that happens every Monday is seven tasks, or one
you keep moving. The calendar has recurrence; tasks do not.

**Reminders depend on a job runner.** They are written and scheduled, and
delivery depends on the background runner being connected on your deployment.
Confirm one arrives before relying on it.

**Attachments need object storage configured.** Without it the rest of the task
works and files are simply unavailable, rather than failing at the moment you
try to add one.

**It is not a project management suite.** No board templates, no automation
rules, no burndown. It is a place to track work that sits next to the mail the
work came from.