Browse documentation

Task list scopes

Filter in-flight work, blockers and retained task history without losing context.

The project Tasks page is server-scoped. Its default URL has no query string and loads In flight work only: active, review, revision, and ready tasks.

  • ?status=open loads queued Open work.
  • ?status=closed loads retained Closed history.
  • Individual in-flight statuses use their existing values, such as ?status=review.
  • Existing explicit ?status=current links remain compatible and load Open plus all in-flight statuses; current was not silently redefined.

Changing a status or another URL-backed filter uses normal page navigation, so reloads and browser Back/Forward restore the same view. In every status view, Previous and Next to the right of the status badges move through 20 matching tasks at a time. On narrow screens, the controls sit below the badges. The server applies all filters and the selected sort before choosing a page. Changing filters or sort returns to the first page.

The list can show a limited number of visible stack relatives for context; they do not count toward the 20 matches. Open a task to inspect its full stack. Select all matching tasks on this page excludes context rows and does not select tasks on other pages. Changing pages clears the selection.

Status badges show exact totals across all tasks visible to the viewer and intentionally do not change with target or people filters. Quick-view badges are exact visible in-flight project totals. Target and people menus come from visibility-scoped distinct aggregates rather than from the currently loaded status rows. The deleted-user creator filter matches visible tasks from any deleted account.

Filter → Blocks selects a visible blocked task and loads its direct, retained blockers: Blocks #369 shows tasks that block #369, not tasks #369 blocks. The chooser lists only visible, non-closed tasks that currently have at least one retained, visible, non-closed direct blocker. Closed, removed and hidden-only blocker relationships do not create options. The default relation view uses the Current status scope so queued Open blockers appear alongside in-flight work; choosing a status, target, owner, creator, or review filter narrows that relation normally. An explicitly selected status remains selected when the relation is added or removed and through Back/Forward navigation. The URL and active pill identify the selected task, and visible stack relatives may still appear as context without becoming blocker matches. Hidden tasks are excluded from both the selector and results. If the selected relationship becomes stale, the URL and pill remain selected but the result fails closed with an empty-state explanation; it never widens to the ordinary task list or reveals hidden tasks.

The project event stream refreshes the current route. This keeps entries, departures, totals, facets, and stack context coherent when a task changes status; the browser never treats one scoped payload as the whole project task set.

The Tasks header, filters, status controls, and any active selection bar stay above long lists as the page scrolls. The list uses the normal page scrollbar, not a second vertical scroll region; the surrounding app shell must not become a scroll container either. The sticky header has no divider beneath its status totals. On narrow screens the quick views, status chips, and active filter pills can scroll horizontally to keep the header compact; on very short viewports the header scrolls normally so it does not obscure the tasks. Keyboard focus on rows clears the sticky controls.

Task rows show conflict, incomplete dependency progress, and approval labels in one wrapping inline flow after the title. Dependency progress appears as blocked <closed>/<total>. The aggregate counts every retained incoming blocking relationship, including blockers the viewer cannot inspect, but never exposes blocker identities, task numbers, titles, or links. Related and removed links do not count. A blocker closed without merging counts as closed. The indicator disappears when every blocker is closed, no blockers remain, or the blocked task closes. Link changes and blocker closure refresh the affected visible task without publishing hidden blocker details.

An open task that directly blocks visible open tasks adds blocks followed by the first three task numbers in ascending order and +N more when needed. The count and numbers include only targets visible to the current viewer; hidden, closed, and removed targets contribute nothing and are not disclosed. The outgoing label is plain row content rather than nested links, so the task row remains the single navigation target.

A conflicts badge means Git verified a conflict with the task’s base. An unmarked row is not a merge verdict. Merging checks the current base.