Search

A box sits in the top bar, beside the project name. Type in it and the hits arrive on the keystroke — no button, no waiting, no page of results. Press Enter and the task opens.

What it looks at

Three things, in this order of preference:

1. The key, which is the address a person says out loud. DP-4 finds DP-4, and so does a bare 4 — that is the half people actually type.
2. The title, first the titles that start with what you typed, then the titles that carry it anywhere.
3. The description. A hit found only there carries the line it was found on, under the title, so a row always says why it is a hit.

Nothing else is searched: not comments, not checklist items, not the values of properties. A property is what filters are for.

Archived tasks are searched too, and they say so on the row.

Two words narrow

Every word has to be somewhere — the key, the title or the description — exactly as every filter rule has to pass. login guide finds the task whose title is “Write the login guide”; it does not find everything with “login” in it as well.

The words may land in different places. One in the title and one in the description is still a hit.

It reaches past the filter

A search looks at every task in the project, and not at the tasks the view happens to be drawing.

That is the difference between a search and a filter, and it decides this. A filter says what a view shows, and everybody on that view sees it. A search hides nothing, writes nothing, and ends by opening one task — so narrowing it to the current view would mean that a key somebody sent you in chat quietly finds nothing, on any board that has a filter on it.

What it owes you instead is a word. A hit the view is not drawing says not in this view on its own row, and still opens.

It finds archived tasks

An archived task is on no board and in no list, so a search is the way back to one. Its row says archived, and opening it shows the panel with the Put back row at the top.

The archive page lists them all; the search is the way to one you can name. Archived is the stronger of the two words — a task no view can draw is not merely outside the one you are looking at — so a row never says both.

The box is in the top bar on purpose

The Filter pill lives in the view strip because a filter belongs to a view. What a search finds belongs to the project, so its box sits above the strip, beside the project name — with the things that no view owns.

The keys

Key	What it does
/	From anywhere on the board, put the cursor in the box. It does not land in the box as a character — unless you were already typing in a field, in which case the field keeps it.
↑ ↓	Move down the hits. The list is a ring, like the filter panel’s.
Enter	Open the highlighted task.
Escape	Put the list away and leave the box. The board and the task panel are untouched.

Opening a task closes the list and keeps the words, so working through three hits in turn is /, ↓, Enter and no retyping.

What it costs

Nothing on the server. The board is already in your browser — every task, with its description — so the search runs there and answers between keystrokes.

That is also its limit: it can only find what the board loaded, and a board loads every task at once. The day a board pages, this becomes a query.

The task panelTitle, description, checklist, comments, activity — and the Agent tab.