Flow: subtasks, checklists and tags
Breaking a big task into parts makes it easier to manage. Flow has three tools for this: subtasks — separate tasks with their own assignee, due date, and status, linked to a parent task; a checklist — a list of items inside a single task that you simply tick off; and tags — short words like "UI", "urgent", or "customer" that you later use to find and filter tasks. This article explains how to enable them in a type, how to work with them in the card, and where they show up on the board and in the table.
Which one to choose
Tool | When it fits | What it has |
|---|---|---|
Subtasks | Part of the work is done by someone else, has its own due date, or needs a separate discussion | Everything a task has: assignee, status, fields, files, discussion, history |
Checklist | Steps of one task done by one person: "review the contract", "send the invoice" | Item text, check mark, who checked it and when, order |
Tags | You need to label tasks quickly and find them by a trait | Up to 20 tags per object, suggestions from tags already in use |
You can turn a checklist item into a subtask at any time — see "Make a subtask" below.
Subtasks
Where subtasks already exist
Subtasks work in a type that has a "many to one" relation to itself: a subtask has one parent, and a parent can have any number of subtasks. This relation already exists:
for tasks in workspaces created from the "Tasks" and "Simple tasks" templates (including the personal Main workspace);
for types created from the ready-made "Tasks" and "IT tasks" descriptions.
If a type has several such relations, the oldest one is used for subtasks.
How to enable subtasks in your own type
If a type has no subtasks, the "Schema and fields" and "Relations" tabs of the type settings show the hint "Tasks of this type have no subtasks. Enable them — the card will get a list of subtasks, and the board and table will get a "3/5" counter." and an "Enable subtasks" button. The button is visible to anyone who can change the type's schema (usually a workspace admin).
One click does everything at once:
creates a relation from the type to itself;
adds two fields to the schema — "Parent task" and "Subtasks" (named in your interface language);
adds the rule "A task cannot be completed while it has open subtasks".
From here there are two cases:
There is no schema draft — Flow publishes a new schema version right away, and objects move to it as usual. Notification: "Subtasks are on: cards now have a "Subtasks" block."
There is an unpublished draft — the fields go into the draft, and Flow says: "Subtask fields were added to the schema draft. Publish it to show subtasks in cards." Click "Publish" on the "Schema and fields" tab. In this case the rule about closing the parent is not created — you can add it later on the "Rules" tab.
The button does not change existing objects: they simply get new empty fields.
The "Subtasks" block in the card
In a type with subtasks, the card has a "Subtasks" block below the main form:
next to the heading — a "closed/total" counter, for example "3/5";
a list of subtasks: each has a check mark (closed ones are checked and struck through), a linked title, and a status; an archived subtask is marked "archived";
the "New subtask and Enter" field: type a title and press Enter — Flow creates a task of the same type, already linked to this one. You become the assignee; fill in the rest in the subtask's card;
if the open object is itself a subtask, there is a "Parent task:" line above the list with a link to the parent.
While there are no subtasks, the block says "No subtasks.". The subtask relation is not repeated in the "Relations" column on the right — it appears only in this block.
A subtask counts as closed when it is in a status of the "completed" or "canceled" kind. The counter includes only subtasks you can see and excludes archived ones. Only direct subtasks count: subtasks of subtasks are not included in the parent's counter.
The "cannot close the parent" rule
In templates and in types where subtasks were enabled with the button, the rule "A task cannot be completed while it has open subtasks" applies. While a task has subtasks that are not "completed" or "canceled", the transition to a final status is unavailable: the transition button in the card shows a lock, and Flow explains why ("Close the subtasks first"). The rule does not stop you from canceling the parent.
You can turn the rule off on the "Rules" tab of the type settings — like any other rule.
How to link and unlink a subtask
You can also choose the parent from the subtask itself: the "Parent task" field in the card or in the creation form is a regular relation field with a "Select" button. A subtask has only one parent, and the chain cannot loop: a task cannot become a subtask of its own subtask. If you break these rules, Flow shows the error "Allowed number of relations exceeded" or "The relation creates a cycle".
If the parent is archived, its subtasks stay where they are; they just lose their link to it.
Subtasks on the board and in the table
Board — the task card shows an icon with a "3/5" counter. When all subtasks are closed, the icon is highlighted. The tooltip on hover reads "Subtasks: 3 of 5 closed".
Table — a column named after the "Subtasks" field shows the same counter. Without a saved view, it sits right after the title; in a view with its own columns, you add it by the field key (usually
subtasks). You cannot sort by it, and it is not included in CSV export.
Tasks without subtasks do not show a counter.
Checklist
Where checklists exist
A checklist is a field of the "Checklist" type. In new workspaces created from the "Tasks" and "Simple tasks" templates, and in types created from the ready-made "Tasks" and "IT tasks" descriptions, tasks already have "Checklist" and "Tags" fields. They are not added to existing workspaces automatically — add them to the type as described in "How to add fields to a type".
Checklist in the creation form
In the "New object" form, the checklist is the "New item and Enter" field. Each Enter adds an item; you can check an item right away or remove it with the cross. All items are saved together with the object when you click "Create".
Checklist in the card
In the card, the checklist is a separate block with the field name (for example, "Checklist"), a "checked/total" counter, and a progress bar. Here every action is saved immediately, without a "Save" button:
add — type text in the "New item and Enter" field and press Enter;
check — the checkbox to the left of the item; to uncheck, use the same checkbox;
rename — double-click the text or choose "Rename" in the item menu (three dots). Enter saves, Esc cancels;
reorder — drag the item by the handle on the left or choose "Move up" / "Move down" in the menu;
delete — "Delete" in the item menu;
make a subtask — "Make a subtask" in the menu (available if subtasks are enabled for the type).
Hover over a checked item to see who checked it and when: "Checked by Anna, 26.09.2026 14:05". Flow records who checked an item and when on its own, and this data cannot be faked; if you uncheck the item, the record is cleared.
A checked item is struck through. A checklist with no items that you cannot change says "No items.".
Make a subtask
The "Make a subtask" menu item creates a subtask with the item's text and removes the item from the checklist. Flow reports "Subtask "…" created", and the subtask appears in the "Subtasks" block right away. This helps when a step turns out bigger than expected and needs its own assignee or due date: checklist items have neither.
Working at the same time
Several people can check different items of the same checklist at the same time — they do not overwrite each other's marks. But if you change an item that someone has just changed or deleted, Flow says: "The item has already been changed. The current checklist is shown — please try again." — and shows the latest version.
Limits
A checklist holds no more than 100 items. If you try to add the 101st, Flow reminds you: "A checklist can have no more than 100 items."
Item text is up to 500 characters.
Items have no assignee or due date — use subtasks for that.
Where else the checklist shows up
Board — a "2/7" icon on the card. If fields are selected in the view's card settings, the icon appears only for the selected checklists; without that setting, for all of them.
The object's History — a checklist change is recorded as a field change, with values shown as progress, for example "2/7 → 3/7".
Filters — the "Checklist" field has its own operators (see below).
CSV export — each item on its own line within the cell:
[x] textfor a checked item,[ ] textfor an unchecked one. Import understands the same format and treats a line without brackets as an unchecked item.
Tags
How to add tags
The "Tags" field consists of chips and a "Tag and Enter" input:
type a tag and press Enter or a comma — the tag becomes a chip; you can paste several at once, separated by commas;
the cross on a chip removes a tag, and Backspace in an empty input removes the last tag;
as you type, Flow suggests tags already used on other objects of this type, most frequent first. Pick a suggestion so you don't end up with "UI", "ui", and "Ui".
In the card, tags are saved with the "Save" button together with the other fields.
How Flow keeps tags tidy
Leading and trailing spaces are removed, and several spaces in a row inside a tag are collapsed into one.
A repeat of the same tag in a different case is dropped: the first spelling is kept.
An object can have no more than 20 tags, and a tag can be up to 50 characters. Once there are 20 tags, the input hints "No more than 20 tags". An admin can lower the limit for a field (the
max_itemssetting, from 1 to 20, in "Other settings (JSON)").
Suggestions are collected only from objects you can see, excluding archived ones — other people's hidden tags are never revealed through suggestions.
Tag colors
A tag's color is picked automatically from the Sensever palette based on its text (case-insensitive). So the same tag has the same color on the board, in the table, and in the card for every member. You cannot choose a color manually.
Tags on the board and in the table
Board — up to four tags on a card; the rest collapse into a "+N" chip. Like checklists, tags are shown for the selected card fields, or all of them if nothing is configured.
Table — the field's column shows tags as colored chips. Tags cannot be sorted or edited right in the cell.
CSV export — tags separated by
;. Import understands both;and,as separators.
Filtering by tags and checklists
In the "Filters" builder of the table, board, calendar, and timeline, these fields have their own operators:
Field | Operators |
|---|---|
Tags | contains any of, contains all, is none of, is empty, is filled |
Checklist | has unchecked items, all items checked, is empty, is filled |
Examples:
"Tags — contains any of — urgent, customer" — tasks with at least one of these tags;
"Checklist — has unchecked items" — tasks where the step-by-step work is not finished yet.
Tags are compared exactly, including spelling — which is why suggestions keep one spelling per tag. "All items checked" is also true for a task with an empty checklist.
In reports and dashboard tiles, you can group by tags: a task with several tags goes into the group of each of them. Learn more in Flow: reports, SLA and business calendar.
How to add fields to a type
A checklist and tags are added to any type like regular fields:
Open the type settings → the "Schema and fields" tab → "+ Field".
Enter a name, for example "Checklist" or "Tags".
In "Data type", choose "Checklist" or "Tags".
Click "Save" in the field window, then "Publish".
You can have several fields of each kind: for example, "Acceptance checklist" and "Launch checklist" — each gets its own block in the card. Learn more about fields and publishing in Flow: object types and fields.
To show tags and the checklist on board cards, select them in the view's card fields or leave the card fields unconfigured.
Permissions
Anyone who can see the object can see its subtasks, checklist, and tags. The "3/5" counter and the subtask list include only subtasks you are allowed to see.
Anyone who can create objects of this type can add subtasks; a new subtask is created with your permissions.
Anyone who can edit the object and the field can check and edit checklist items and add tags. If the field is read-only for your role, the checklist checkboxes are inactive and there are no input fields.
Subtasks cannot be added to an archived object, and its checklist and tags cannot be changed.
Enabling subtasks in a type and adding fields requires permission to manage the type's schema.
Learn more about roles in Flow: members, roles, teams and billing.
What's next
Flow: the object card — the other blocks of the card.
Flow: recurring tasks — tasks that create themselves on a schedule; the checklist is copied into the new task without check marks.
Flow: table, board, calendar and filters — filters and views.
Flow API: subtasks, checklists and recurrence — the same operations through the API.
মন্তব্য