Lithora
Lithora Docs

Task Management

The atomic unit of work in Lithora. Tasks are more than just checkboxes; they are connected nodes in your project graph.

Core Concepts

  • Task Key: ID formatted as PROJ-123. Unique across the workspace.
  • Assignees: Multiple assignees supported. The first assignee is the "Primary Owner".
  • Priority: P0 (Urgent), P1 (High), P2 (Normal), P3 (Low).

Task Relationships

Tasks do not exist in a vacuum.

Projects

Tasks roll up to Project completion %. If a task is blocked, the project status may flip to "At Risk".

Docs

You can embed tasks directly into documents using /task. Completing it in the doc updates the board.

Dependencies & Blocking

Lithora enforces strict dependency logic:

  • Blocked By: Task B cannot be started until Task A is done.
  • Blocking: Task A is preventing Task B from starting.
If you attempt to close a task that has open blockers, Lithora will prompt you to resolve dependencies first.

Automations

Tasks are the primary trigger for Automations. Common workflows:

  • When status changes to "Done" → Notify #slack-channel
  • When priority is "Urgent" → Assign to Team Lead
  • When task sits in "In Progress" for > 5 days → Flag as "Stale"

Time Tracking Linkage

If Time Tracking is enabled, a "Start Timer" button appears on the task detail. Time logged here aggregates to the Workload View and Billing Reports.