Creating and editing tasks
New task, or pressing N anywhere, opens the task form. Only the title is required — everything else can wait until the work is real.

The fields
Section titled “The fields”| Field | Notes |
|---|---|
| Template | Pre-fills title, description, category and acceptance criteria from a project template. Pick it first — it overwrites what is already in the form. |
| Title | The only required field. |
| Description | Markdown. Accepts pasted and dropped files — see below. |
| Status | Which column the task lands in. Defaults to the first column. |
| Priority | Low, Medium, High, Urgent. Medium by default. |
| Category | One of the project’s categories. |
| Assignee | Anyone with access to the project. Assigning someone also makes them a watcher. |
| Due date | Shown on the card once set. |
| Sprint | Leave empty to keep the task in the backlog. |
| Repeats | Daily, weekly or monthly. The task recreates itself when it reaches a done column. |
| Checklist | The acceptance criteria. Each line becomes a tickable item and drives the progress bar on the card. |
| Custom fields | Whatever the project defines. Required fields block saving until they are filled. |
AI Assist
Section titled “AI Assist”If the instance has an AI key configured, the form opens with an AI Assist box at the top. Describe the work in a sentence — “let customers export their invoice history as a CSV” — press Generate, and every field below is filled in for you to review.

It writes a title, a description, acceptance criteria, a category and a difficulty. Nothing is saved until you press save, and every field stays editable.
The more interesting part is what it notices about the rest of the board:
- Possible duplicate — when the task looks like one that already exists, you get the task key and a sentence explaining why. In the screenshot it spotted that the CSV export belongs inside the billing tab work rather than beside it.
- Suggested dependencies — tasks that should be finished first (Blocked by), or that this work would block, with the reasoning.
Both are suggestions, not actions. The agent has read the project’s existing tasks to produce them; it is up to you whether to accept, adjust, or ignore.
Attachments
Section titled “Attachments”The description accepts files directly: paste an image from the clipboard, or drag a file onto the box. It uploads and leaves a Markdown link in place, so a screenshot of the bug sits inside the task that reports it. This works both in this form and in the description on the task detail.
The PM agent chat also accepts pasted attachments.
Comments are text only — Markdown and @mentions, no file upload. Put the picture in the description.
Editing later
Section titled “Editing later”Everything above can be changed after the fact from the task detail, where the description saves as you type and the details rail carries the same fields. Some fields are also editable without opening the task at all: status and assignee from the list view, status and sprint from the card’s right-click menu.