Skip to content
ARGUS User Manual

Tasks tile

The Tasks tile is the richest collab surface. It’s a task board with a full state machine, specialised editors for drone-sweep and waypoint tasks, SITREP (situation report) submissions per task, progress tracking, and linking to map polygons.

What’s in a task

Each task card shows:

  • Title + description preview.
  • Type icon + label — one of 10 types (see below).
  • Priority chip — colour-coded: critical (red) / high (orange) / medium (yellow) / low (grey).
  • Assigned asset dots — first 3 + overflow badge.
  • Scheduled duration — “18:00–19:30” or similar.
  • Linked polygon chip (if the task references a map polygon).
  • Progress bar — 0-100 %.
  • Status badge — Pending / Briefed / En Route / Active / Paused / Completed / Aborted / Failed.

The 10 task types

The New Task form presents a grid of task-type tiles:

  • Operative — generic operator task.
  • Drone sweep — auto-flies a coverage pattern inside a polygon.
  • Drone waypoint — explicit multi-point flight path.
  • Medevac — medical evacuation, flags routing + personnel.
  • Observation.
  • Comms setup.
  • Traffic control.
  • Search.
  • Custom.
  • Evidence — with chain-of-custody metadata.

Each type produces slightly different forms.

Filters + sort

  • Status tabs across the top — All / Pending / En Route / Active / Paused / Done / Aborted.
  • Text search — matches title + description, case-insensitive, substring.
  • Sort — by priority (critical → low) then by creation time newest- first.

Creating a task

Click New Task. Pick a type, fill:

  • Title + description.
  • Priority — picker, 4 options.
  • Assigned assets — checklist of mission participants.
  • Scheduled start + end — datetime pickers.
  • Target label (for location-bearing tasks).
  • Resources — text input + add button, multiple allowed.
  • Notes — free text.

For Drone sweep tasks, extra fields:

  • Pattern — lawnmower / perimeter / spiral / etc.
  • Spacing — distance between lines (m).
  • Altitude (m AGL).
  • Speed (m/s).
  • Bearing (degrees).
  • Linked polygon — the polygon to sweep.

For Drone waypoint tasks, a waypoint list with:

  • Per-waypoint lat / lng / alt fields.
  • Drag-handle reordering (CDK drag-drop).
  • Add / remove buttons.

The status state machine

Tasks move through defined legal transitions:

  • From Pending: → Briefed / En Route / Aborted.
  • From Briefed: → En Route / Aborted.
  • From En Route: → Active / Paused / Aborted.
  • From Active: → Paused / Completed / Failed / Aborted.
  • From Paused: → Active / Aborted.

The detail view shows only the currently-legal next states so you can’t transition illegally.

SITREP per task

In the expanded task view, a SITREP text box lets assigned operators submit a situation report. Submissions append to the task’s SITREP log with timestamp + author. Used for periodic status updates during a long task.

Progress is separately tracked via a slider 0-100 — emit on every slider change.

Linking to polygons + assets

  • Linked polygon chip — click to pan the map to the polygon and highlight it.
  • Assigned asset chips — click to jump to the asset in the fleet tile.

Permissions

No explicit commander-only gating — any mission participant can create, edit, or delete tasks. Aspirational role-gating is planned.

Persistence

Firestore: missions/{missionId}/tasks/{taskId}. Progress, SITREP, and status transitions all persist in real-time.

Known limitations

  • No drone-mission auto-upload — drone-sweep tasks with full sweep params don’t currently upload to the drone’s GCS automatically. You plan in the task; execute via the drone-mission planner.
  • No SITREP analysis — SITREPs are plain-text records; the copilot doesn’t yet parse them for insights.
  • No per-user personal view — all tasks render for everyone; there’s no “my assigned tasks only” filter.