Status automations: actions on entry and exit
In Fluo, status automations change a task when it enters or leaves a column: they assign someone, set a deadline, change the type and tags. A column has one set of them for tasks of any type.
How to set up status automations
- On the board, click “⋮” in the column header and choose “Status automations”. If some automations are already on, the number next to the item shows how many.
- In the “Status automations” window, open the “When it arrives” or “When it leaves” tab.
- Turn on the action you need with its switch and fill it in.
- Click “Save”.
The other two tabs, “To get in” and “To leave”, hold the conditions without which a task can't enter the column or leave it. They and the checks done by people are covered in “Conditions and checks: what holds a task”.
You can also open the window from the workflow map: click the lightning bolt next to a column on a board of the map. If the column has no automations yet, the bolt appears when you hover over the column. In the “Link” panel, the “Change” button in the “Leaves …” and “Arrives in …” cards opens it, see “Link rules: conditions and actions on the way”.
After you save, a lightning bolt appears in the column header. Hover over it, and the tooltip lists what the column does, for example “Closes the task on entry”. If the plan doesn't include status automations, the bolt is faded and the tooltip says “Not active on the current plan”.
What the column does when a task arrives
The actions on the “When it arrives” tab run whenever a task arrives in the column: from another column of this board, from another board along a link or without one, from Inbox and from a desk.
| Action | What it does |
|---|---|
| “Add a check” | Adds a checklist item to the task that the assigned people tick. Until they tick it, the task won't leave the board. See “Conditions and checks: what holds a task” |
| “Close the task” | Marks the task as done the moment it arrives. The nested “Reopen the task when it leaves the status” switch is on by default. A recurring task moves to its next date and returns to the column you choose, “The first status of the board” by default |
| “Assign the task” | Makes “A selected member”, “The task author” or “Whoever moved the task” the assignee. “Nobody (remove the assignee)” clears the assignee |
| “Send a notification” | Notifies the task author, the assignee and selected members; you can add your own text. Whoever moved the task does not get the notification |
| “Change tags” | “Add tags” adds the selected tags, “Remove tags” removes the selected ones or all of them. You can create a new tag right in the window |
| “Change priority” | Sets the selected priority |
| “Change the task type” | Sets a project type or “No type”. From then on, the task follows the route of the new type, see “Task types: create, choose, change” |
| “Change the deadline” | “Set in N days” at the chosen time, or “Remove the deadline”. Days are counted from the day of the move, in the time zone of whoever moved the task |
| “Fill in fields” | Fills in the description, the epic and the custom fields of this board, except file fields. An empty value clears the field. A number field gets the next number if the task has none yet |
| “Start the timer” | Starts the timer of whoever moved the task, whether they are the assignee or not. See “Time tracking: timer and logging time” |
| “Move tasks closed with a checkmark here” | A task closed with the circle on its card moves to this column by itself. Only one column of the board can collect closed tasks |
What the column does when a task leaves
The “When it leaves” tab has almost the same actions as arrival: “Change the assignee”, “Send a notification”, “Change tags”, “Change priority”, “Change the task type”, “Change the deadline” and “Fill in fields”. The exit notification says where the task went. Two actions exist only here.
- “Uncheck the checklist items”. The checklist items become unticked again, for example when the task is returned for rework.
- “Pause the task timers”. Runs on any move out of the column.
When exit actions run
Every exit action except pausing the timers has its own “Works” setting.
| Option | When it runs |
|---|---|
| “On any move out” | On any move out of the column, including leaving the board: to Inbox, to another board, to a desk |
| “On a move forward” | On a move to any column of this board to the right of this one |
| “On a return back” | On a move to any column of this board to the left of this one |
| “On a move to selected columns” | Only on a move to the columns of this board that you select |
“Forward” and “back” follow the order of the columns on the board. A move to another board triggers only “On any move out”.
Example: the assignee changes by itself
This is how you set up what used to be the automatic assignee change. Say Amy reviews the tasks in the “In review” column.
- Open the status automations of the “In review” column.
- On the “When it arrives” tab, turn on “Assign the task”, choose “A selected member” and pick Amy.
- On the “When it leaves” tab, turn on “Change the assignee” and choose “The task author”.
- In the “Works” field, choose “On a return back” and click “Save”.
Now every task that reaches review goes to Amy. If Amy returns it to a column further left, the task author becomes the assignee again. When the task moves forward, the assignee stays the same.
What wins on a move along a link
When a task moves along a link of its route, three sets run: the automations of the column it leaves, the rules of the link itself and the automations of the column it arrives in. Exit actions run first, then arrival actions. If both columns change the same thing, the arrival column has the last word. A link has its own rules (Link rules: conditions and actions on the way), and for some actions it wins over the column.
- Assignee and deadline. If the link has them on, the task gets them from the link, and the same action of the arrival column does not run for it.
- Type. The link's type wins over the arrival column's type. If the type changes on arrival, “Change the task type” on exit does not run.
- Tags are set by the column first, then by the link.
- There is one arrival notification: the recipients of the column and the link together, with the link's text, or the column's text if the link's is empty.
- Checks from the column and from the link are added together.
- Closing, the timer, priority, fields and collecting closed tasks exist only on the column.
The “Status automations” window shows this. If an incoming link sets the assignee, type or deadline itself, the column's action carries a note such as “Tasks moved along the link ‘For signature’ get the assignee from the link”. If tasks move on from this column by themselves, the top of the window says along which link, and that right after they arrive, the rules of that link and the automations of the next status apply too.
When status automations don't run
- The task was created right in the column. Automations run only when an existing task is moved.
- The task was reordered within the same column.
- The space is not on the Business plan. The lightning bolt in the column header is faded.
- An exit action has a different option in “Works”.
- A task moved by itself to the column that collects closed tasks, or a recurring task returned to its column. The automations of the column it arrived in don't run in that case.
- The move was undone with the “Undo” button in the notification. Status automations don't run then, and what they did on the move is rolled back, see “How a task moves along its route”. A regular move back doesn't roll anything back and runs the automations like any move.
When several tasks are moved at once, no notifications are sent; the other automations work.
Status automations and task types
A column has one set of automations for all task types. If an action is needed only for tasks of one type, set it on a link of that type's route: link rules run only on a move along that link. See “Link rules: conditions and actions on the way”.
What you see after an automatic close
If the column closes tasks, after the move Fluo shows “The task was closed automatically in the ‘Done’ status”. Closed tasks are hidden on the board by default, so the card disappears from the column.
Related articles
On the website: Cross-team processes in Fluo: linked boards without code
Linked from
- How to complete and reopen a task
- Boards, columns and statuses
- Closed tasks: where they go and how to show them
- Column task limit (WIP)
- Project workflow: task routes and task types
- Connectors: passing tasks between projects
- Board workflow: allowed transitions within the board
- How to link a task to an epic
- Quick questions on each screen
- Workflows, routes and automations: all articles
- Fluo glossary