Skip to main content

Tasks & views

Tasks are how work is tracked inside a project. Each task (or subtask) has a stable key, a lifecycle status, and optional metadata — assignee, priority, dates, labels, linked repos, and agent runs. Views are saved combinations of filters, grouping, sort order, and layout so everyone can open the slice of work that matters to them in one click.

Tasks

Status lifecycle

Move tasks through statuses as work progresses. Subtasks follow the same statuses as parent tasks.

StatusMeaningTypical next step
BacklogCaptured but not scheduledMove to Planned when prioritized
PlannedCommitted for an upcoming cycle or milestoneStart work → In progress
In progressActively being worked onOpen PR → In review, or flag Blocked
In reviewCode or design review in flightMerge/ship → Done
BlockedWaiting on a dependency or decisionUnblock → In progress
DoneCompleted and accepted—
CanceledWill not be done; kept for history—

Priority and dates

PriorityWhen to use
UrgentProduction incident or release blocker
HighCurrent cycle commitment
MediumImportant but schedulable
LowNice-to-have or cleanup
NoneTriage queue — priority not yet set

Optional start, due, and target dates drive calendar and timeline views. Pair due dates with cycle or milestone fields when your team plans in fixed iterations.

Categories

Tasks carry a category (issue, bug, feature, improvement, chore) for reporting — it does not change permissions or workflow. Use categories in views to separate product work from maintenance.

Linking agent runs

Tasks can link to agent runs started from the project. When a run completes, its summary and PR link appear on the task so reviewers have context. This is especially useful for CLI and cloud agent handoffs:

# Start a run and attach it to a task key (pattern — exact flags on CLI download page)
4rged agent run \
  --project atl-platform \
  --task ATL-184 \
  --prompt "Implement retry backoff per ATL-184 acceptance criteria"

Contract alignment

Task and subtask types in the Projects app mirror platform contracts (X4rgePmWorkItem in packages/platform-contracts). Work items are always task or subtask at the entity level; category (issue, bug, feature, improvement, chore) is metadata for views and reporting only. Status slugs (backlog, planned, in-progress, in-review, blocked, done, canceled) match the PM schema so agent-run links and future API exports stay consistent across dashboard, CLI, and cloud surfaces.

Views

A view is a saved query over tasks: filters + layout + group + sort.

LayoutBest for
ListDense triage, bulk edits, export-friendly review
BoardKanban by status, assignee, or priority
TimelineMilestones, dependencies, and date-driven planning
CalendarDue-date visibility across the team
Group byExample use
StatusClassic board columns
AssigneeStandup — "what is everyone holding?"
PriorityEscalation review
Milestone / cycleRelease or sprint scope
CategorySeparate bugs from features

Creating a shared view

  1. Filter to the slice you need

    In the Projects app, open a project and apply filters — for example status In progress or Blocked, assignee me, due date this week.

  2. Choose layout and grouping

    Switch to Board grouped by Status, or List grouped by Assignee for standup. Set sort to Priority or Due date as appropriate.

  3. Save the view

    Click Save view, name it (e.g. "Eng standup" or "Release blockers"), and choose whether it is personal or shared with the project. Shared views appear in everyone's view picker.

  4. Iterate

    Adjust filters as the team matures — pin the two or three views people open daily rather than maintaining dozens of stale saved queries.

Example views teams reuse

View nameFilter / layoutAudience
My active workAssignee = me; status in Planned, In progress, or In review; listIndividual contributors
BlockersStatus = Blocked; board grouped by assigneeLeads, standup
Release candidateMilestone = current; sort by priority; timelinePM + eng lead
Agent queueLabel = agent; status = Backlog; listTeams using CLI/cloud handoff

Triage with the agent

Use the agent inside a project to accelerate PM work without leaving the codebase context:

  1. Summarize blockers

    Ask the agent to read the current Blocked view and produce a short list of dependencies and suggested owners.

  2. Draft a plan

    Point it at open High / Urgent tasks and request a sequenced action plan with risks.

  3. Propose status updates

    For In review items, ask for a concise status blurb you can paste into Slack or a weekly report — the agent can reference linked PRs when repos are connected.

Note

Agent suggestions for task changes are advisory. Accept or edit outcomes in the task UI; accepted PM recommendations are recorded in the project audit trail where PM is enabled.

Subtasks for large work

Break epics into a parent task and subtasks for reviewable chunks. Subtasks inherit the project key prefix (e.g. ATL-184 → ATL-184-a) and roll up status on the parent board column.

Projects overview

Project lifecycle, repos, and agent scope.

Members & roles

Who can create tasks, manage views, and assign work.