Boards, tasks and cards

Project views

Open a project and use the tabs at the top:

On Kanban and Timeline, the epic filter narrows the view to one epic or shows All work. The choice is kept in the page address, so you can share a link to a filtered board.

Epics, tasks, bugs and subtasks

Planner uses a Jira-style hierarchy of four task types:

• Epic — a large piece of work or a feature. Has an owner, an optional goal and a colour, and contains tasks and bugs.
• Task and Bug — the everyday units of work, usually inside an epic.
• Subtask — a step of a task or bug. Subtasks can't have children.

Every task has a key made of the project's short code and a number — WEB-42. The key is what you search for, mention and hand to the CLI. A task's type is fixed once it is created.

The Kanban board

• Columns are the statuses of the project's workflow, in the order they are laid out in the workflow designer. To add or rename columns, edit the workflow (custom workflows).
• Lanes: each epic gets its own collapsible lane, plus Other tasks for work without an epic.
• Drag and drop a card to another column to change its status, or up and down to reorder it. Cards stay in their epic's lane — change the parent in the task to move it to another epic.
• Quick add: press Add task in a column, type a title, Enter to save, Esc to cancel.
• Click a card to open the task.

The timeline

The timeline plots each task from its start date to its due date. Zoom between Day, Week and Month. Drag a bar to move it in time, or drag either end to change the start or due date. Tasks without dates show a Set dates placeholder.

Inside a task

The task window has two panes. On the left, the content:

• name and description;
• its subtasks (or, on an epic, its tasks) with a button to add one;
• linked work items, attachments, and the docs pages that mention the task;
• comments.

On the right, the details:

• Status and type;
• Assignees (with Assign to me) — on an epic, the epic owners;
• Labels — free-form tags, up to 20 per task, 40 characters each;
• Parent, start date and due date (the due date can't be before the start);
• Colour (inherits from the epic if blank) and, on epics, the epic goal;
• Template and its custom fields (card templates).

The header shows the parent chain as a breadcrumb, the task key and a button to copy a link to the task. Drag the divider between the panes to resize them; double-click it to reset.

Descriptions and comments

Descriptions and comments use a rich editor. Type / for the block menu: headings, bullet and numbered lists, a QC checklist, quote, code block, table, callout, status lozenge, image, divider and smart link.

• Paste from anywhere — including Jira: formatting is kept and pasted images are uploaded to Planner.
• Smart links — paste the link of a Planner task, a docs page or a GitLab wiki page and it becomes an inline card.
• Tables — Ctrl+Alt+arrow inserts a row or column next to the current cell.
• Comments are listed oldest first. You can edit or delete your own; edited comments are marked “edited”.

Developers and AI agents can also read and write a whole task as Markdown — see the CLI.

Linked work items

Link a task to another with Relates to or Is blocked by — type a key or name, or paste the other task's link. The other task shows the reverse (“blocks”). Links also appear in the Markdown version the CLI downloads, so an agent can check what is blocking a task before starting.

Docs pages that mention a task

When a docs page links to a task (by its link or by #KEY), the task lists that page under Linked pages.

Attachments

Drop files onto the task window, click to choose them, or paste a screenshot straight in. Each file can be up to 50 MB. Evidence uploaded by the CLI (test videos, screenshots, logs) appears here too.

Deleting a task