Board columns and task fields
The two sections that decide what your board looks like and what a task can say.
Columns
Section titled “Columns”Settings → Board. Add a column, rename it, pick its colour, reorder it with the move controls, and give it a role.
The role is the important part. Automation — workers, the PM agent, agent instructions — keys on the role, never the label, so you can call a column Ready for dev or Shipping and nothing downstream breaks. Each column carries exactly one of backlog, approved, active, review, blocked or done.
A column can also be marked to trigger a PM review, which is what feeds the autonomous handling of tasks landing in a human-review column.
Categories
Section titled “Categories”Settings → Task fields. Categories are the task types — bug, doc, user-story and idea by default — each with a colour. Rename them, add your own, drop the ones you never use. They are per project.
Custom fields
Section titled “Custom fields”
Anything else you want to record on a task. Each field has a type — text, number, date, dropdown, multi-select or checkbox — and three switches that decide where it shows up:
| Switch | Effect |
|---|---|
| Show on card | The value appears as a chip on the board card. |
| Show in list | The field gets its own column in the list view. |
| Filterable | The field appears as a control in the filter panel. |
Fields can be marked required, reordered, and archived — archiving hides a field from new work without destroying the values already recorded against it.
A dropdown named Difficulty with options S, M, L and XL is worth creating on day one: it drives the dashboard’s difficulty panel, and agents use it to decide whether a task needs a plan before code.
Task templates
Section titled “Task templates”Also under Task fields. A template pre-fills title, description, category and acceptance criteria — the fastest way to make sure every bug report has reproduction steps.