Skip to content

Tasks

Each project has a task board (kanban-style) to plan and track work. Who drafts the statement, when is the expert report due? Put the procedural steps in your project as tasks — with deadline, priority, and assignee — and nobody on the matter misses a term again. This area used to be called “Kanban”; the application now labels it Tasks.

A project's task board with columns and tasks

The /kanban URL keeps working as a legacy alias alongside /tasks. Existing links stay valid.

You open the board from inside a project via the Tasks tab.

You can typically:

  • create columns,
  • rename columns,
  • delete columns (with confirmation),
  • reorder columns.

Tip: keep it simple. A classic setup:

  • To do
  • In progress
  • Review
  • Done

A task can include:

  • title,
  • description,
  • linked document (optional),
  • assignee (optional),
  • due date (optional),
  • priority (low/normal/high/urgent).

You can:

  • create and edit tasks,
  • move tasks between columns,
  • archive or delete tasks (depending on UI and permissions).

Link a task to a document when:

  • the document is the evidence or source,
  • you want everyone to use the same reference,
  • you want quick navigation from task to source.

Project documents have an optional Review status column (see Projects) that pairs well with tasks for tracking what still needs review.

In project chat you can mention tasks using # (or #"..." for names with spaces).

Helpful prompts:

  • “Split this task into 5 subtasks with priorities.”
  • “Write a checklist for this task and reference relevant documents.”

More: Chat.