Skip to main content
Guide

Lists, Tasks & Boards

Last updated 16 days ago

Lists, Tasks & Boards ​

Lists are the central place in Liza for organizing work — from a single task to the big picture.

Lists ​

A list groups related tasks together and comes with its own chat, files, and dates. Examples: "Backlog", "Sprint 42", "Onboarding".

Tasks (Items) ​

A task is a single entry in a list. It can have:

  • Assignment to one or more people
  • Status (open / in progress / done)
  • Priority and due date
  • Sprint and story points – see Sprints
  • A short description (a sentence or two — AI agents write here too) and a page for longer content such as notes, a briefing or a concept
  • Tags, subtasks, and its own chat history

Tasks can be nested (subtasks) and categorized with tags.

Planning beyond a single list

A task always belongs to exactly one list. To plan across lists in windows of time, use sprints – they lie across projects.

Boxes on a task ​

To the right of a task sits an info column with boxes – small areas you add via "+" in the header, rename, and remove again. Each task gets exactly the tools it needs:

BoxWhat for
SessionThis task's AI session: job queue, running plan, chapter history.
Todo listShared sub-tasks – persistent and visible to everyone.
Cloud DriveThe task's files (also where AI-generated files and images land).
PagesNotes and documents for this task.
BrowserCollected links.
ArtifactsArtifacts produced by the AI.
GitCommits, uncommitted changes and pull requests. The shared part (commits/PRs from GitHub) is visible everywhere, local changes only in the desktop app.
Local folderA folder on your machine – desktop only.
TerminalA real shell – desktop only.
ServerStart and stop this task's dev servers and read their logs – desktop only (see coding agents).
ApprovalsWho was asked for approval and how they decided – created automatically with the first approval request.

Approvals ​

Some work needs an okay before it counts as done – from the client, your boss or the team lead. For that you ask individual people for approval, much like a review on GitHub.

Requesting: in a task's menu choose Request approval from … and pick a person. You can choose anyone in the project – members, owners and guests (guests only for tasks that aren't internal). Only the person you pick is asked and notified. If you need several approvals, ask one after the other. You can also ask more people via the + in the Approvals box. Private tasks can't be sent for approval – the people asked wouldn't be able to see them.

The "Approvals" box: with the first request the task gets this box. For every person asked it records when they were asked, how they decided, when and with which comment. The task moves to "Review" and shows Awaiting approval – whoever is asked sees Your approval.

Deciding: the person asked approves or requests changes (with a comment) – in the box, on the message in the task chat or, as a guest, in their overview.

  • The task is done only once everyone asked has approved.
  • If someone requests changes, the task goes back to "In progress".
  • If you ask again after that, a new round starts. Anything still open in the old round is then shown as "superseded" in the box; the rounds stay visible one below the other.

Boards & Cards ​

The same content can be displayed as a board: cards in columns (sections) — ideal for a Kanban-style overview. Move cards via drag and drop to change their status.

Views ​

Depending on your needs, you can switch between list, board, and timeline views. You can filter specifically for overdue tasks and tasks assigned to you.

Linking with chat

A task can be created directly from a message in team chat — so nothing gets lost in the conversation.