Tasks & Views

Task IDs

Each task has a short ID made of the project's prefix and a number: in a project with prefix KPL, tasks are KPL1, KPL2, KPL28 and so on. Open questions get a Q after the prefix (KPLQ3). Use these IDs in commands and AI chat.

IDs show as green pills. Click a task ID to open the task, or a question ID to open that question. In lists where the pill copies the ID instead, a click puts it on the clipboard.

/ct KPL2

Close task KPL2

/et KPL1 -prio 1

Set KPL1 to critical

what's KPL3 about?

Ask AI about KPL3

View Modes

Toggle with header buttons or press V.

Task Interactions

Click

Open the detail panel for full editing

Right-click

Opens command bar with /et VISUAL_ID prefilled

Drag

Move a task to another category (Categories view)

Hover timer

Quick-extend deadline (+1h, +2h, +1d)

Closing requisites

Must confirm completion before closing

Auto-save

All changes save automatically

Refresh

The refresh button on the task page and side panel reloads the task. If you have unsaved changes, it asks before throwing them away.

New task with AI

In the new task form, describe the task in your own words. Karea AI fills in the title, description, priority, status, category, tags, deadline and more for you to check, or creates it directly. Pro and Max plans.

Priority Levels

On tasks, priority shows as short coloured text, like this:

P1Critical

P2High

P3Medium (default)

P4Low

P5Minor

Task Statuses

backlogSaved for later

openNot started

in_progressWorking on it

blockedWaiting on something

reviewWaiting for review

doneCompleted

cancelledDiscarded / not doing

Parent finished, subtasks not

A task in Review, Done or Cancelled says there is nothing left to do. If one of its subtasks is still anywhere else (Open, Doing, Blocked or Backlog), that is not true yet, so the task shows an amber warning triangle next to its status: on the board, in the All Tasks list, in the side panel and on its own page. Hover it to see which subtasks are still open, e.g. "In review, but 2 subtasks are still open: KA12 (Doing), KA13 (Open)". Projects with their own statuses are judged by what each status stands for, so a custom "QA" that maps to Review counts as Review. The icon goes away by itself as soon as the last subtask reaches Review, Done or Cancelled. Closing or cancelling a task that still has open subtasks always asks first: close them all, close only this task (it leaves the dashboard and shows the warning), or cancel. The AI chat asks the same in words, chat commands take -subtasks all or -subtasks only, and the MCP close actions take closeSubtasks.

Review stages

Review is the one status that hides a whole process behind a single word. A task sitting with the person who wrote it, a task sitting with a colleague and a task sitting with the client are three different situations - different waits, different people to chase - and the board used to render all three identically. The review stage is that missing word.

developer_reviewDeveloper review

peer_reviewPeer review

client_reviewClient review

· These are the built-in stages. Each project can create, rename, reorder and delete its own from Projects → Statuses → Review stages, or turn the whole feature off, in which case Review behaves exactly as it always did.
· A stage only exists while the task is in Review. Moving it out clears the stage; moving it in picks the first one unless you name another, however the change is made: board, bulk edit, AI chat, MCP or API.
· Hover the status pill on the board: a task in Review offers the next stage, and a task one step before Review can go into Review and straight to a chosen reviewer in a single click.
· On a task's own page the status pill stays, and the stage gets its own pill right beside it in the stage's colour.
· Over the AI and MCP: /et KA12 -reviewstage client, or the reviewStage field on the karea_edit_task action (in karea_tasks_write). Naming a stage moves the task into Review if it is not there yet.
· Every change is written to the task history as its own entry, so a week spent passing a task from the developer to a peer to the client reads as three steps rather than one undifferentiated block. Reporting has a Tasks in Review by Stage chart for the same reason.
· Renaming or deleting a stage does not move the tasks sitting in it. They keep the stage they were put in and history stays readable.

Public task sharing

Share a task with anyone via a public link. Open the task detail panel and use the Public link section to generate a shareable URL. You can choose whether to include notes and whether to allow anonymous visitors to post notes. The shared page shows the task's full details in a clean, read-only view. Revoke the link at any time to remove access.

Activity heatmap

Each task shows how much happened on it, day by day. A brighter day means more real work, not just more clicks.

Weighs most

Adding notes, subtasks, resources, meetings or linked tasks, adding closing requisites, and closing the task.

Weighs some

Changing the status, the assignee or the description, editing a note, ticking a requisite, adding a work session.

Weighs little

Small edits such as the deadline, title, priority or tags. Repeating the same edit on the same day barely adds anything, and AI context updates have a small daily cap.

Settings

Show seconds in timers

Toggle seconds in deadline countdown timers

Default view

Categories or Priority as your default project view

Third table status

Which status gets its own section in Priority view

Notifications

In-app toasts, browser push, and email alerts