Tasks & the board

The backlog: manual and imported tasks, your own statuses and priorities, and running work from a card.

The backlog is where work waits, whichever door it came in through — typed by hand, imported from a tracker, filed over the API, or captured from Slack. Every task keeps its origin, and each origin keeps its own vocabulary.

Creating tasks

New task (editor sidebar, dashboard Tasks page, or the phone) takes a title and description plus — where they exist — status, priority, assignee, and workflow. Assignees are your organization's members; the workflow picker appears once the project has more than one. Create and run does both in one click.

Manual tasks are yours to edit and delete. Imported tasks are read-only in Peractor — the tracker stays the source of truth, so you move the issue on its own board and Peractor follows within seconds.

Your board, your columns

Peractor ships with no built-in statuses — until you define columns, the task list is a flat list, which is all a solo flow needs. Define statuses in the editor's Statuses view or the dashboard's Tasks → Statuses tab, one YAML per column in host-stored project config:

# status/in-spec.yaml
id: in-spec
name: In Spec
icon: file-text
color: blue
order: 20

With statuses defined, the Peractor panel becomes a board: every column renders (empty ones too), plus a "No status" column for strays. Columns are more than filing — workflow phases can trigger on a column and move tasks to another, so dragging a card is how work starts. See status automation.

Connected trackers get their own panels alongside — each mirroring that tracker's real board: Linear's workflow states, a Jira project's statuses, a GitHub Projects board's columns. No mapping table, no translation; a task lives in its origin's vocabulary.

Priorities and assignees

Priorities are a per-project list (Tasks → Priorities) with a built-in Urgent / High / Medium / Low fallback, so the field always works. Imported tasks carry their tracker's priority and assignee where the tracker has them.

Running work from a card

Every task row offers Run and Run with workflow…. A task holds one active run and the full history of earlier ones, each replayable read-only. See the run lifecycle.