Tasks

Tasks

Tasks are the actionable work surface of Pizarra. They provide explicit ownership, state, hierarchy, milestones, attributed notes, and durable history. Active team-owned workflow steps project into tasks so owners can use one board for planned and unplanned work. A console-owned human gate receives a notice without creating a task.

Create and inspect work

Assign a task:

tiza task add builder "Implement request validation" --milestone hardening

Create unassigned backlog work with -:

tiza task add - "Evaluate the next storage migration"

Create a subtask:

tiza task add tester "Add negative request cases" --parent 41

List and inspect:

tiza task list open
tiza task list open builder
tiza task list all @release
tiza task show 41

The group form filters across visible group members.

Report progress as durable notes

tiza task note 41 "Implemented strict duplicate-key rejection."
tiza task note 41 "Release build passes; isolated integration test is next."

Notes are append-only, timestamped, and attributed to the authenticated actor. They are useful for:

• human review;
• handoff between owners;
• explaining evidence behind a state change;
• workflow stall detection; and
• preserving decisions that would otherwise stay in terminal scrollback.

A fresh note on a linked active workflow task resets its silence clock for stall reminders.

Assignment and state

tiza task assign 41 reviewer
tiza task done 41
tiza task reopen 41

Task states are open strings. In the current engine, done, superseded, and cancelled are terminal states.

Assignment and state changes on workflow-linked tasks are gated by workflow authority and lifecycle. Closing a linked active task goes through the same completion path as tiza wf done; it cannot bypass dependency or evidence rules.

Parent and deletion integrity

Delete an eligible standalone task:

tiza task delete 41

Deletion is refused when:

• the task has subtasks;
• a workflow still links to it; or
• the operation would violate current work integrity.

Deleting an eligible workflow unlinks its task projections but does not erase task history.

Tasks versus workflows

Use a task when:

• work is independent;
• no activation graph is required;
• a simple owner and status are enough; or
• the item is an interrupt or backlog candidate.

Use a workflow when:

• work has dependencies, branches, or joins;
• an entire phase must finish before the next;
• strict completion evidence is required;
• a human approval gate matters;
• errors must freeze the plan;
• repair needs independent verification; or
• snapshots and plan export are useful.

The two systems are intentionally connected. Workflow truth is authoritative for dependency execution; task cards remain the owner's convenient operational surface.

Example: from backlog to verified plan

tiza task add - "Prepare version 1.3 release"
tiza task assign 52 operator
tiza task note 52 "Scope accepted; converting the work into a release workflow."

tiza wf create release-1-3 release
tiza wf step release-1-3 builder "Build candidate" --after 0
tiza wf step release-1-3 tester "Run upgrade matrix" --after 1
tiza wf step release-1-3 reviewer "Review compatibility" --after 1
tiza wf step release-1-3 console "Approve publication" --after 2,3
tiza wf set release-1-3 strict on
tiza wf start release-1-3

tiza task done 52

Browser board

The pzweb Tasks view provides filters, cards, notes, assignment, state changes, creation, and guarded deletion over the same hub state.

Continue with Workflow Engine and Web Console. Exact command syntax is in docs/cli.md.