Fields
Task and project fields
Section titled “Task and project fields”Field reference for the default web client. Where to edit points to the user guide section.
Last updated: August 30, 2026
Core fields (tasks and projects)
Section titled “Core fields (tasks and projects)”| Field | Tasks | Projects | Where to edit |
|---|---|---|---|
| Title | ✓ | ✓ | Task detail → Title; quick-add (tasks only) |
| Description | ✓ | ✓ | Task detail → Description |
| Status | ✓ | ✓ | List row status icon (non-terminal); task detail → Status; kanban column. Labels come from org definitions (Settings → Statuses & priorities). |
| Priority | ✓ | ✓ | Task detail → Priority; list column. Labels come from org definitions (Settings → Statuses & priorities). |
| Assignee | ✓ | ✓ | Task detail → Assignee; list column |
| Due date | ✓ | ✓ | Task detail → When (due date, repeat, Remind me) |
| Goal date | ✓ | ✓ | Task detail → reference rail (Goal date); not inside When |
| Display ID | ✓ | ✓ | Read-only; list and modal title |
| Kind | task | project | Set at creation (quick-add vs new project modal) |
| Parent | ✓ | ✓ | Implicit via hierarchy drill-down and create context |
Time signals: Due, Goal, Open, Originally due, Reviewed, Created, and Completed each answer a different job (and reset differently). Semantics live in time-signals.md — do not re-narrate that table here.
Status and priority (org-customizable)
Section titled “Status and priority (org-customizable)”Each organization defines its own status and priority lists. Tasks store a stable key (e.g. todo, high); members see the org label (e.g. Todo, High).
Default keys (seeded on org create):
| Kind | Keys | Notes |
|---|---|---|
| Status | todo, in_progress, done, canceled | UI label for canceled is Canceled (US English). |
| Priority | none, low, medium, high, urgent |
Owners and admins may add custom keys, rename labels, reorder, and hide options. Keys cannot be renamed after create. Hidden options stay on existing tasks but are not offered for new edits.
Status categories (set when creating a custom status; defaults use the table above):
| Category | Meaning |
|---|---|
active | Open work — list quick-status cycling, review views, dependency blocking |
complete | Finished — terminal for show-completed, search filters, recurrence completion |
canceled | Canceled — terminal (same semantics as complete for filtering) |
At least one visible complete status, one visible canceled status, and a visible none priority must remain. Definitions in use by tasks cannot be deleted.
Where to edit: Settings → Organization → Statuses & priorities (?section=org-workflow-options) — owner/admin only.
Project-only
Section titled “Project-only”| Field | Where to edit |
|---|---|
| Color | New project modal; task detail → Project color (swatch picker). Shown in sidebar tree and hierarchy breadcrumb segments. |
Task-only
Section titled “Task-only”| Field | Where to edit |
|---|---|
| Recurrence | Task detail → When → Repeats (requires due date). Daily/weekly/monthly/yearly presets; Weekly uses Repeat on; Monthly/Yearly can use calendar day or weekday-of-month. Save schedule / Stop repeating. Completing a repeating task rolls due date forward. |
| Remind me | Task detail → When → personal reminder timing (org Policies set morning-of vs evening-before) |
| Originally due | Read-only under When after the first due is rescheduled (date only; no elapsed tally) |
| Open | Optional list Open column; muted Open line in task detail Provenance (instance elapsed time) |
| Dependencies | Task detail → Depends on — add/remove prerequisites; Blocked badge when incomplete. |
| Pinned | Task detail header pin (per-user); also @pinned: on quick-add. Surfaces in the workspace Pinned strip. |
| Reviewed | List Last reviewed cell; @reviewed on quick-add sets reviewed_at at create. |
| Private | Task detail attribute bar — org-wide visibility (see user guide § Private). From a project folder, use Project details / Open details to reach the bar. |
Related data (not columns on the task row)
Section titled “Related data (not columns on the task row)”| Field / entity | Where to edit |
|---|---|
| Tags | Task detail → Tags — apply org tag, create new tag (name + color), remove from task |
| Links | Task detail → Links — URL + optional label; scheme normalized on save |
| Comments | Task detail → Comments — post, edit own, delete own; owners/admins delete any |
| Custom fields | Org admins: Settings → Organization → Custom fields — define fields; Visible hides org-wide without deleting data; Delete removes the definition. Members: Settings → Display — hide fields in personal task detail (visual only). Task detail → typed editors; undefined keys under Legacy fields (JSON) |
| Permissions | Task detail → Permissions (owners/admins or effective admin on resource) |
| Provenance | Task detail — created/updated by and timestamps (read-only) |
Extension-gated (Task scoring)
Section titled “Extension-gated (Task scoring)”When Settings → Organization → Extensions → Task scoring is Available or Mandatory:
| Field / output | Where to edit |
|---|---|
| Impact, Effort (Impact×Effort method) or Impact, Confidence, Ease (ICE) | Task detail → Scoring section; list columns when enabled |
| Score (derived) | Read-only in list when the Score column is on; computed from the enabled axes |
When the extension is Off, axis values stay stored but the UI hides them. Follow-ups (matrix views, RICE, etc.): SOMEDAY.md § Task scoring follow-ups.
Organization Activity, task Change history, and Profile Recent activity are shipped (see user guide).
Org and user settings (not task fields)
Section titled “Org and user settings (not task fields)”This file is the task/project field locator. For the Settings rail inventory (?section= map — Profile through Delete organization), see user-guide.md — Settings.