Checklist, comments and attachments
Detail a task with steps, conversation and files — and understand the limits of each one.
A card’s panel has three detail sections, each with its own purpose.
Checklist
The checklist is the task’s list of steps. Its progress appears on the closed card — “3 of 5 done” — which makes it the cheapest way to show progress without opening anything.
- Add step — write the text and confirm with Add.
- Toggle done — marks and unmarks the step.
- Edit the step — fixes the text without losing the state.
- Remove the step — removes the entry.
Each step has its own identifier; an operation that points to a step that no longer exists is refused instead of changing another one.
Comments
Comments are the conversation about the task — including the conversation with agents.
- Comment publishes what is written in the field.
- Edit comment changes the text; the comment then appears marked as edited.
- Remove comment deletes the entry.
The section also records when a comment came from an agent, and shows yours as yours. An empty comment is refused — write something before sending.
Attachments
Attachments are of two kinds:
| Kind | How it gets in |
|---|---|
| File | Attach file picks a file from disk |
| Link | Attach link records an http(s) address |
For each attachment there is Show in folder (reveals the managed copy on disk) and Remove attachment.
What happens to your file
The file is copied, not moved. The copy lives in the application’s data, and the original is never moved nor deleted — neither when attaching, nor when removing the attachment, nor when deleting the task. That is why removing an attachment is not a risky operation for your file.
Limits
- 20 MiB per file.
- 200 MiB per board.
- 20 attachments per item.
An attachment that is too large is refused with a message, not truncated.
The gotcha of the attachment with a remote workspace
The path you provide for Attach file must be readable by the machine where the application runs. In an SSH workspace, that means the path of your computer — not the path of the file inside the remote machine. Passing a remote path makes the copy fail, because the file does not exist on this side.
Links must be http or https addresses. Another scheme is refused.
Scope and limits
- Nothing here creates a workspace. Checklist, comment and attachment live on the board.
- A link attachment is not downloaded. The board keeps the address; the content belongs to the destination, and it can change or go offline.
- The file attachment is a copy. Changing the original after attaching does not change what is on the board, and vice versa.