Browse documentation

Find work in a project

Search for a task and use status and blocker views without losing context.

Find work by topic before choosing a task to take. Search is a discovery aid: it matches visible task content but cannot prove that no related work exists. The browser's Tasks page and the CLI show different scopes of the same project work; neither turns stack context into a filter match.

Discover, then inspect

rp task search 'notification delivery'
rp --json task show <number>

Read the task's context, ownership, branch and status before acting. In a connected checkout, use rp task list --status open for an Open queue and rp task take <number> only when you intend to start that work. See the first-task guide for the full work turn. The task commands reference lists the other search and list options.

Read the browser task list

Dashboard and Tasks show task rows before checking Git conflicts. Conflict badges can appear after the page loads. A missing badge is not proof that a task can merge; the server checks again when you merge.

An individual task opens with its title, status, and recent conversation. On long threads, select Show earlier entries to read the rest. Stack and readiness details, code changes, and people pickers can appear after the conversation. You can submit a review even if Code changes fails to load. The server checks that your verdict applies to the submitted commit and that the branch still points to it. The server also checks merge eligibility when you merge.

The default project Tasks view shows In flight work (active, review, revision and ready). Select Open or Closed to load those status scopes; changing the filter updates the URL, so reload and Back/Forward preserve it. Project totals remain totals, even if a target or person filter narrows the rows. Stack relatives may appear to explain a matching row without themselves matching the filter.

Filter → Blocks selects a task that currently has visible, retained, non-closed direct blockers. Blocks #369 shows tasks blocking #369, not tasks #369 blocks. The default relation view includes queued Open blockers as well as in-flight ones; other filters can narrow it. A stale selected relationship yields an explanation instead of silently widening to all tasks. Hidden task details are not exposed by the filter. Use task stacks and links to distinguish merge blockers from branch ancestry.