User guide
Tasks and board
Tasks are on a Kanban board in the Tasks tab of the project page. Claude pulls the same tasks through the API — the board and Claude work on one list.
Columns and status
A task has one of six statuses. The column on the board is not a field of its own but follows from the status:
| Status | Value in the API | Column on the board |
|---|---|---|
| On hold | hold | Backlog |
| Not started | todo | Backlog |
| In progress | in_progress | In progress |
| Question | question | In progress |
| To review | review | Review |
| Done | done | Done |
“On hold” and “Not started” are both in the backlog and mean different things: a task on hold waits for a condition (field “Waiting for”) and is not pulled by Claude; a task not started is. Only Claude sets “Question”; the status cannot be chosen by hand.
You drag a card into another column with drag & drop; the status changes with it.
Assignee and area
Every task is assigned to someone: Owner, Staff, Claude or External. “Hand over to Claude” on the card gives it to Claude. The area (Frontend, Backend, Design, Infra, Support) appears as a label on the card. The filter bar above the board filters by assignee, status and area; “Reset filters ×” clears everything.
Creating a task
“+ New” › Task (key a) or on the board: title (at least three characters), description in Markdown and images. The status “Not started” is preset; if you choose “On hold”, enter the condition under Waiting for. Tasks created through the API need a meaningful title of at least 25 characters; VentionDesk recognises very similar open tasks as duplicates.
The detail view
A click on the card opens “Task #N” with status, area, assignee, due date, estimate, title, description and images, the history of all results and — if there is one — “Open pull request”. Attachments are images (PNG, JPEG, WebP). “Delete task” asks once more.
Results from Claude
Claude reports the state of a task with one of six results. Each one appears in the task’s history; some change the status:
| Result | Shown as | Effect |
|---|---|---|
arbeitet | Still working | Progress update. The task stays “In progress”. |
kontrolle | Needs review | Implemented and shipped. Status “To review” (Review column); requires evidence. |
frage | Question for you | Question. Status “Question”; the task is not pulled again until someone answers. |
master | For the owner to do | With the owner, without a status change — for example a step Claude has no access to. |
blockiert | Blocked | Cannot continue. The task stays “In progress” and is with a person. |
erledigt | Done | Done. Status “Done”; requires evidence. |
“Needs review” and “Done” require evidence — for example the commit or the result of a measurement. A “done” without evidence is not a completion but a claim.
Approval or rejection
To “Question”, “Needs review”, “For the owner to do” and “Blocked” you answer in the detail view with approval or rejection. The buttons are named differently depending on the occasion:
| Occasion | Approval | Rejection |
|---|---|---|
| Question from Claude | “Approve — do it this way” | “Reject” |
| Claude asks for a review | “Approve — tick off” | “Reject — rework” |
| Claude hands over to you | “Done — back to Claude” | “Reject” |
| Claude cannot continue | “Solved — back to Claude” | “Reject” |
An approval during review sets the task to “Done”, a rejection there sets it back to “Not started” with Claude; any other answer returns the task “In progress” to Claude. A rejection requires a comment, an approval does not. You attach images to your answer directly.
How Claude pulls tasks and reports back is described under Claude and MCP.