Conditions and checks: what holds a task
In Fluo, conditions and checks hold a task: until they are met, the task can't be moved into a column or out of it.
Fluo verifies conditions by itself, for example whether fields are filled in. A check is ticked by a person, for example a lawyer.
How to add a check
A check is a checklist item that the assigned people tick. This is how approval works in Fluo: a lawyer, an accountant or a director ticks their check, and the task moves on.
- On the board, click “⋮” in the column header and choose “Status automations”.
- On the “When it arrives” tab, in the “Add a check” block, click “Check”.
- Write what is checked, for example “Lawyer” or “CEO signature”.
- In the “Who ticks it” row, click “Member” and pick the people.
- If there are several people, choose “any of them” or “all of them” in the “Ticked when” row.
- If the mark needs an explanation, turn on “With a comment”.
- Click “Save”.
A column can have several checks, each with its own people. The trash icon to the right of the title removes a check you don't need.
What a check does
When a task arrives in the column, Fluo adds the check item to its checklist. Below the item you can see who ticks it, for example “Check: any of Amy, Paul”, and the note “holds the task on the board ‘Legal’”. The assigned people get a “Waiting for your mark” notification, and in My tasks these items are collected in the “Waiting for my mark” view.
Until the check is ticked:
- the task won't leave the board: not to another board, not to Inbox, not to a desk;
- within the board, it can't be moved along a route link that starts in this column. An ordinary move between columns of the board without a link is not held by the check;
- you can always return the task to a place it has already been. A return asks for a comment, and the marks on the checks of the board the task was returned from are reset. When the task gets there again, it is checked again. Undoing a move with “Undo” in the notification isn't a return: no comment is needed, the marks stay, and checks that a rule added during that move are removed.
Only the assigned people can tick a check, and only while the task is on the board of that check. With “any of them”, one mark is enough; with “all of them”, everyone has to tick. Only the person who ticked can remove the mark. A check “With a comment” can't be ticked without a comment, and the comment goes to the task chat.
A check holds the task only on Business and during its trial. If the plan changes to Free Team, the item stays in the checklist with the note “does not hold the task: not active on the current plan”.
If the task leaves the column and comes back, the check is not duplicated. A ticked check stays ticked.
Checks and changing the task type
Column checks stay with a task of any type. Checks added by a route link (Link rules: conditions and actions on the way) are dropped after the type changes if the new route doesn't have them. Such an item is marked “dropped when the task type changed” and no longer holds the task.
How to set conditions
- Click “⋮” in the column header and choose “Status automations”.
- Open the “To get in” tab if a task shouldn't get into the column, or “To leave” if it shouldn't get out.
- On the “To leave” tab, use the “Check” field to choose on which move out the conditions are checked.
- Turn on the conditions you need and fill them in.
- Click “Save”.
The “Check” field has the same options as the exit actions: “On any move out”, “On a move forward”, “On a return back” and “On a move to selected columns”. What each one means is explained in “Status automations: actions on entry and exit”. For example, “The checklist is fully done” with “On a move forward” won't let the task move on, while it can always be returned for rework.
Which conditions there are
| Condition | The task passes if |
|---|---|
| “The checklist is fully done” | All checklist items are ticked, checks included. Items dropped when the type changed don't count |
| “The task has an assignee” | An assignee is set |
| “The task has no active blockers” | The task has no blockers. See “Blockers: how to mark a task as blocked” |
| “All previous tasks are closed” | The tasks that come earlier through relations between tasks are closed. See “Related tasks and task chains” |
| “Related tasks are closed” | All related tasks are closed: previous, next and parallel |
| “Time is logged on the task” | A timer ran on the task or time spent was noted in its chat. This condition exists only on the “To leave” tab |
| “Required fields” | The selected fields are filled in: description, deadline, tags, epic or custom fields of the board |
| “Field values” | The task's fields match the conditions you built |
| “A file is required” | A file was attached for this requirement |
| “The task has a deadline” | The task has a deadline. With “and it is not overdue” ticked, the deadline hasn't passed either |
| “The task has a tag” | The task has any tag (“any tag”), one of the selected tags (“one of”) or all of them (“all of”) |
| “A comment is required for the move” | Whoever moves the task wrote a comment. It goes to the task chat |
Conditions on field values
In the “Field values” block, click “Condition”, choose a field, then a comparison and a value. This is how you set, for example, “Amount greater than 1,000,000” or “Priority: High”. If there are several conditions, choose “all conditions” or “any one of them” in the “Must hold” row.
You can compare priority, assignee, task type, deadline, tags, title, description and the custom fields of the board. Numbers are compared by value and range, lists by the selected options, dates by day, text by what it contains. For any field you can check whether it is filled in or empty. One set can have up to 20 conditions.
Links and branches use the same condition builder, see “Branches: different paths by condition”.
A file on request
In the “A file is required” block, click “File” and describe which file is needed, for example “A signed scan of the contract”. Next to it, choose where it goes: “To the task attachments” or into a file field of this board. There can be up to 10 file requirements; “Another file” adds the next one.
Only a file attached while the task is in the column it is moved from counts. Older attachments don't count. You can attach it right in the “To move to …” window that opens when the task is moved.
When conditions are checked
Conditions are checked on any move of a task between columns: by dragging, in the task window, along a link, when several tasks are moved at once, through the API and MCP. When a task moves along a route link, the conditions of the column it leaves, of the link and of the column it arrives in add up. One comment on the move is enough, even if several rules ask for it.
Conditions are checked before the column and link actions run. So “The task has an assignee” on the “To get in” tab won't let a task without an assignee in, even if the column assigns someone itself.
Conditions are not checked in these cases:
- the task is created right in the column;
- the task is reordered within the same column;
- a task closed with a checkmark moves by itself to the column that collects closed tasks, or a recurring task returns to its column;
- the space is not on the Business plan.
If a field was removed from the board, the condition about it is no longer checked: such a field can't be filled in on the board.
How the person moving the task sees conditions and checks
While you drag a card, the columns show where you can drop it, where you can't and why. If something holds the task, the “To move to …” window opens. In it you can tick checklist items and your own check, fill in fields, attach a file and write a comment right away. See “Why a task isn't transferred”.
Related articles
On the website: Cross-team processes in Fluo: linked boards without code