Source: https://fluotask.ru/en/help/588-how-a-task-moves-along-its-route
Updated: 2026-11-15

# How a task moves along its route

In Fluo, a task follows the route of its type: you move it along a link by hand, and a link with “The task moves on by itself” moves it without you.

Who can use it

Anyone who moves tasks on the task's board can move it. Along a link of its route, a task can also go to a board that's closed to you. Links are drawn on the Pro and Business plans, see “[Workflows and plans](https://fluotask.ru/en/help/596-workflows-and-plans)”.

## How to move a task along a link

1. On the task card, to the right of the completion circle, click the round arrow. It's there when links of the task's route lead out of its column.
2. In the “Move task forward” menu, choose a column. The column name has its board name under it.

The Design board, In review column: the round arrow on a Feature task card is numbered 1, and the open Move task forward menu with the Backlog column of the Development board 2

The task goes to the top of the chosen column. The “Task moved!” notification appears with the “Undo” and “Go to board” buttons.

The same menu opens when you right-click the card (the “Move to” item) and in the “Status” field of the task window.

## What the move menu shows

- At the top are the links of the task's route out of its column. For a task with “No type,” these are the links of the “No type” route; for a task with a type, only the links of its type. Links of other routes aren't in the menu.
- The “Send back” group lists the columns where the task has already been. See “How to return a task” below.
- The “Other columns” group has the columns of the task's own board and the connector exits of its route.
- If a column won't accept the task, the line under it says how many requirements aren't met. Click such a column to open the “To move to” window, see “[Why a task isn't transferred](https://fluotask.ru/en/help/589-why-a-task-isnt-transferred)”.
- If there's a fork after the column, its branches are grouped under the fork's label. The matching branch is available, the others are dimmed with “Does not fit:” and the condition. See “[Branches: different paths by condition](https://fluotask.ru/en/help/973-branches-different-paths-by-condition)”.

## Moving a task outside its route

The route doesn't forbid other moves. You can drag the task to any column of its board, or move it to a board that's open to you with the selection panel or a bulk action, see “[How to move a task to another board](https://fluotask.ru/en/help/522-how-to-move-a-task-to-another-board)”.

Link rules don't run on such a move: they work only for moves along that link. Column conditions and checks always hold the task, and you can't bypass them. A task goes to a board that's closed to you only along a link of its route.

## How a task moves by itself

On the workflow map, you can turn on “The task moves on by itself” for a link. The line of such a link shows a paper plane icon. How to turn it on is described in “[Link rules: conditions and actions on the way](https://fluotask.ru/en/help/972-link-rules-conditions-and-actions-on-the-way)”.

The task moves along such a link as soon as nothing holds it:

- if the column and the link have no conditions or checks, the task leaves as soon as it lands in the column;
- if there are conditions, it waits until they're met: a checklist item is ticked, a field is filled, a file is attached, a check is marked;
- link rules and status automations run on this move, just as on a manual move;
- from the next column, the task can move on the same way. The chain goes up to six steps at a time and never enters the same column twice.

Along a link into a connector, the task also moves by itself: through the connector, it lands in a column of the receiving project, and the “Task types at the exit” table sets its type at the exit. If the connector has no exit for this type, the task stays in the column. More in “[Connectors: passing tasks between projects](https://fluotask.ru/en/help/591-connectors-passing-tasks-between-projects)”.

Animation: a card is carried from the Code review column to Ready for testing, the column hint says Will move on to Testing / Queue, the card leaves the board, and the Route notification with the Undo and Go to board buttons appears at the bottom

On such a move, Fluo doesn't ask for the comment that column conditions require. If the link needs a comment, the comment of the move that brought the task into the column counts. Without one, the task waits until someone moves it by hand with a comment.

While the task waits, its card shows a “Waiting:” line with the first reason. Right after a move, Fluo shows the “The task is waiting in ‘…’” notification with the “What is needed to move it?” button. What to do next is described in “[Why a task isn't transferred](https://fluotask.ru/en/help/589-why-a-task-isnt-transferred)”.

## The notification after a move along the route

When a task has moved by itself, the “Route” notification appears at the bottom of the screen: “The task moved on: ‘Board / Column’.” It stays for about eight seconds.

- “Go to board” takes you to the board where the task went. The button is there if it's another board and it's open to you.
- “Undo” returns the task to where it was before your action. This is an undo, not a return: no comment is needed, the task doesn't wait, and check marks aren't reset. If the task type changed first, the old type comes back first.

If the task went to a board that's closed to you, there's no “Undo” button. You can return such a task only from its new board.

What “Undo” brings back

Together with the task, everything that status automations, link rules, and the connector set on the way comes back: the assignee, the deadline, the priority, the epic, the completion mark, the type, tags, field values, the description. Checks added by an automation or a rule and not yet marked are removed. If you or a colleague changed something by hand in the meantime, that change stays. Status automations don't run on an undo.

Checklist marks reset by a status automation, an auto-number already given out, and notifications already sent don't come back. In the task history, the undo lines carry the “Undo” badge.

“Undo” works for 5 minutes and as long as nobody has moved the task. After that, moving it back is a return with a comment. A regular move back doesn't roll back anything the rules did.

## The task route in the task window

A task with a type shows a route line above its title in the task window. It lists the boards of the route in order: a check mark on the boards passed, a dot on the one where the task is now. If a board appears in the route twice, its column is named next to it. You can scroll a long line sideways.

The window of a Feature task: above the title, the route line with Design and Development checked, Testing with a dot and Release next, the line is framed

Under the route line, Fluo writes why the task is waiting. If this type has no further links from the column, you see “From here the ‘…’ type has no further links.” instead of the route. A task with “No type” has no route line.

## How to return a task

You can return a task to where it has already been. You don't need to draw a link back for this: Fluo recognizes a return from the task history. The “Undo” button in the notification after a move doesn't count as a return, see above.

1. Open the move menu: with the arrow on the card, with a right-click, or in the “Status” field of the task window.
2. In the “Send back” group, choose a column.
3. In the “Return to ‘…’” window, write why you're returning the task and click “Return.”

The Return to Development / Code review window: the Why are you returning it field with a comment is numbered 3, and the Return button is framed

What happens after a return:

- the comment goes to the task chat;
- the check marks of the board the task was returned from are reset;
- the task waits in the column and doesn't move on by itself. Its card says “Returned: waiting to be sent on.” When the task is ready, move it on by hand;
- checks don't hold a return.

If you drag a card into a column where the task has already been, the column hint warns you: “Return: the task will wait.”

What Fluo counts as a return

The task's path starts at the latest of these events: creation, reopening after it was closed, a type change. A column of the current board counts as visited only if the task has left this board since then. Moves back and forth within one board stay regular moves.

If you move a task by hand into a column whose “The task moves on by itself” link leads back where it came from, the task also waits there. Otherwise Fluo would undo your move right away.

## Moving a task with FluoAI, the API and MCP

FluoAI, the public API (moveTask) and MCP (fluo_move_task) move a task through the same mechanism as the app:

- the route, conditions, checks, link rules, status automations and connectors all apply;
- the move is written to the task history, so a return is recognized the same way;
- if a comment is needed, pass it in the comment parameter. FluoAI asks you itself why you're moving the task;
- if conditions hold the move, the API and MCP refuse it and list the reasons.

Exceptions:

- you can't move a task through a connector into another space with the API: an API key belongs to one space;
- if you delete a column with the API and move its tasks to another column, they all move at once, without rules or conditions. The app has no such action.

See “Public API: getting started” and “How to connect Claude, ChatGPT and Cursor via MCP”.

## Related articles

- [Project workflow: task routes and task types](https://fluotask.ru/en/help/586-project-workflow-task-routes-and-task-types)
- [Why a task isn't transferred](https://fluotask.ru/en/help/589-why-a-task-isnt-transferred)
- [Link rules: conditions and actions on the way](https://fluotask.ru/en/help/972-link-rules-conditions-and-actions-on-the-way)
- [“Handed off”: where tasks that left the board are now](https://fluotask.ru/en/help/974-handed-off-where-tasks-that-left-the-board-are-now)
- [How to move a task to another board](https://fluotask.ru/en/help/522-how-to-move-a-task-to-another-board)

## Related articles

- [Connectors: passing tasks between projects](https://fluotask.ru/en/help/591-connectors-passing-tasks-between-projects.md)
- [Workflows and plans](https://fluotask.ru/en/help/596-workflows-and-plans.md)
- [Branches: different paths by condition](https://fluotask.ru/en/help/973-branches-different-paths-by-condition.md)

## Linked from

- [The task window: what's in it](https://fluotask.ru/en/help/509-the-task-window-whats-in-it.md)
- [Task card: what it shows](https://fluotask.ru/en/help/511-task-card-what-it-shows.md)
- [How to connect columns of different boards](https://fluotask.ru/en/help/587-how-to-connect-columns-of-different-boards.md)
- [Status automations: actions on entry and exit](https://fluotask.ru/en/help/594-status-automations-actions-on-entry-and-exit.md)
- [Workflows FAQ](https://fluotask.ru/en/help/597-workflows-faq.md)
- [Workflows, routes and automations: all articles](https://fluotask.ru/en/help/695-workflows-routes-and-automations-all-articles.md)
- [Fluo glossary](https://fluotask.ru/en/help/963-fluo-glossary.md)
