Task Management
The atomic unit of work in Lithora. Tasks are more than just checkboxes; they are connected nodes in your project graph.
users lose draft state on refresh; editor is slow on big docs; we should add autosave.
Tasks move through statuses as work progresses — linked PRs and automations can advance them automatically.
Anatomy of a task
- Title & description: A title (up to 200 characters) and an optional description (up to 2,000 characters).
- Assignee: One assignee per task. To split work across people, create a task each and link them — that keeps ownership unambiguous.
- Priority:
Low,Medium(the default),High, orUrgent. - Due date, tags & estimate: An optional due date, up to 20 tags, and an estimate in hours that the Sprint Planner packs against.
Statuses
Every task sits in exactly one of four statuses:
- To Do: Captured and not started. Where new work lands by default.
- In Progress: Someone is actively working on it. Opening a linked PR can move work here for you.
- In Review: Work is done but waiting on review — code review, QA, or sign-off.
- Done: Complete. Merging a linked pull request can set this automatically.
Task Relationships
Tasks do not exist in a vacuum.
Projects
Tasks roll up into a project health score built from completion rate, overdue tasks, velocity, and blocked work. The score reads out as Excellent, Good, At Risk, or Critical.
Docs & whiteboards
Link a task to a doc, a file, or a whiteboard so the context that explains the work travels with it — and so the AI agent can read it when you ask about the task.
Dependencies
API only — there is no dependency UI yet
finish_to_start and start_to_start) and the /api/task-dependencies endpoints are live, but nothing in the app reads or writes them: there is no Dependencies section on a task, no blocked indicator on the board, and no way to add one without calling the API yourself. Treat sequencing as unsupported in the product for now — use automations if you need a rule enforced, and subtasks if you only need to break work down.Seeing tasks in context
Every project shows the same tasks through different lenses — Overview, Board, Backlog, Timeline, Calendar, Tasks, Files, and Integrations. Two are worth calling out:
Timeline
Answers “what ships this quarter, and what is slipping?” — dated work laid out over time so overruns are obvious before the deadline. Timeline view →
Work that arrives by email
Mail sent to the inbound parser becomes a work item with the original thread still attached. Email to work item →
Deleting a task
Deleting a task is a soft delete. It moves to Trash, stays recoverable for 30 days, and is purged on a schedule after that. Restore it yourself from Dashboard → Trash— with one caveat: if the task's project is also in the Trash, restore the project first. Trash & restore →
Automations
Tasks are the primary trigger for automations — task created, updated, assigned, completed, status changed, or a deadline approaching. Common workflows:
- When status changes to “Done” → post a message to a connected Slack channel
- When priority becomes “Urgent” → assign to the team lead and notify them
- When a deadline is approaching → add a tag and send an email
Plan requirement
Time Tracking Linkage
On Pro and Scale, a timer can be started against a task and time logged there feeds the weekly and monthly reports plus the CSV timesheet export. See Time Tracking.