What every card carries
| Element | Description |
|---|---|
| Title | The card's name or subject line (required) |
| Identifier | Auto-generated number (#1, #2, #3...) for easy reference |
| Kind | The card type (e.g., Task, Bug, Feature, Idea) |
| Description | Detailed description with rich text formatting in Markdown |
The title and the description are dimensions too
It is worth knowing early, because it explains a lot of what follows: the title
and the description are not special fields bolted onto a card. They are
dimensions, of the Title and Specification kinds, and they behave like every
other dimension — they appear in the project's dimension list, and you can give
them the label your work actually uses. A recruitment project can call them
Candidate and Notes and nothing else changes.
Dimensions
Dimensions are customizable fields that add structured data to your cards.
Common examples:
- Assignee — Who's responsible
- Status — Current state (To Do, In Progress, Done)
- Due Date — When it's needed
- Priority — How urgent it is
- Progress — Completion percentage
You can create your own dimensions to track anything relevant to your workflow.
Which ones a card shows depends on its Kind — a Bug and an Invoice have no
reason to carry the same fields.
The four faces of a card
Open a card and it offers four tabs. Each is a different question about the same
card.
| Tab | What lives there |
|---|---|
| Card description | The body text, in Markdown |
| Attachments | Every file on the card |
| Linked cards | What this card is attached to |
| History | Every change and every comment, newest first |
Attachments
Cards hold files — documents, images, PDFs, emails, video — and show them in
place rather than making you download them. A card has at most one cover,
and only an image can be one; the cover is the picture the card shows on a
board. Attachments: read every file without leaving the card covers the whole
of it.
History and discussion
Every change to a card is recorded — who, when, and what the value was before.
Comments live in the same stream, so a decision and the change it caused sit
next to each other. One change can be undone, or the whole card rolled back to
a moment, without erasing anything. See Card history: see what changed, and
undo it.
Relationships
Cards can link to other cards, creating parent-child hierarchies:
Epic: Website Redesign
├── Story: New homepage layout
├── Story: Update navigation
│ ├── Task: Design mockups
│ └── Task: Implement CSS
└── Bug: Mobile menu broken
Key Actions
| Action | What it does |
|---|---|
| Create | Add a new card with title and optional details |
| Edit | Modify any card content or dimensions |
| Duplicate | Clone a card with all its data |
| Link | Connect cards in parent-child relationships |
| Comment | Add to the card's discussion, in its history |
| Archive | Hide without deleting (recoverable) |
| Export | Download as HTML, Word, or PDF |