Fluo

Board workflow: allowed transitions within the board

Updated:

The board workflow in Fluo sets which columns of one board a task can move between. When it's on, you can't put a card into a column that no arrow leads to.

Board workflow and routes

Fluo has two maps, and they do different jobs.

  • Routes are drawn on the project's “Workflow” page. They are links between the columns of boards, and each task type has its own route. A route suggests the way and runs the link rules, but you can still move a task outside it. See “Project workflow: task routes and task types”.
  • The board workflow is drawn inside one board. A board has one, and it's the same for tasks of any type. Fluo won't let a task make a move that isn't on the map.

If a route link leads from one column to another on the same board, the board workflow still applies. When it doesn't allow that move, the “Next” item in the move menu is inactive, and a link with “The task moves on by itself” won't move the task.

Status automations are separate from the board workflow. They run even when the workflow is off. See “Status automations: actions on entry and exit”.

How to set up the board workflow

  1. Open the board and click the “Board workflow” button with a diagram icon in the header. It's in the views group, next to the “Kanban” and “List” buttons. On a phone, the board views are in the board actions menu.
  2. The map shows the board's statuses as cards. Arrange them however you like. The layout is saved by itself.
  3. Each card has small round points along its edges. Drag a line from a point on one status to a point on another. That arrow is one allowed move.
  4. The “Transition settings” window opens. In the “Transition name” field, you can describe the action, for example “Send for review”, and click “Save”. Without a name of its own, the arrow shows the two statuses separated by a slash.
  5. Draw all the allowed moves this way. To let a task come back, you need a separate arrow in the opposite direction.
  6. Turn on the switch in the panel on the left. It shows “On”.
The Testing board header: the Board workflow button with a diagram icon in the view buttons is numbered 1
Animation: a line is dragged from a point on the Bugs found card to a point on the In testing card, an arrow appears and the Transition settings window opens
The board workflow map of the Testing board: status cards are joined by arrows, the On switch in the panel on the left is numbered 6, and the Any status card is framed

While the switch is off, the map is only a draft and doesn't restrict the board. Fluo reminds you of this above the map: “The scheme is saved, but it is not applied — turn on ‘Activate the workflow’”. If the workflow is on but has no arrows, the board also moves tasks freely.

“Any status”

On the left of the map there is a gray “Any status” card. An arrow from it lets a task reach a status from any column of the board. This is handy for a status like “Canceled”: a task can go there from any step.

How to change or turn off a transition

Click the label on an arrow. In the “Transition settings” window, you can rename the transition, turn it off with the “Transition is active” switch, or remove it with “Delete”.

The Transition settings window: where the transition starts and ends, with the Transition name field, the Transition is active switch and the Delete button framed

A transition that is turned off stays on the map, but tasks can't be moved along it. This way you can close a transition for a while without erasing it.

To lift the restrictions from the whole board, click the switch in the panel again. The map isn't erased, and you can turn it on again.

What changes on the board

  • While you carry a card, a column with no transition shows a no-entry sign and the hint “Will not let in: the board workflow does not lead here”. If you drop the card, it goes back, and Fluo shows “Transfer is not possible” and “The board workflow does not allow moving from ‘A’ to ‘B’”.
  • In the move menu on a card and in the task window, such columns are inactive.
  • In a bulk move, Fluo skips the tasks that aren't allowed to make the move and warns you about this beforehand.
  • You can always reorder cards within one column.
  • A task that arrives from another board (including along a route link), from the Inbox or from a service desk lands on the board freely. The board workflow only covers moves within the board.
Animation: a card from the Queue column is carried to the Accepted column, the column shows a no-entry sign and the hint “Will not let in: the board workflow does not lead here”, and after release the card returns to Queue

What else is on the map

  • Click a status card to open the “Edit the status” window: name, icon, color and task limit. See “Column task limit (WIP)” for more about the limit.
  • The lightning bolt on a card opens the “Status automations” window. The number next to it shows how many automations are on.
  • The “+” button in the panel, “Create a status”, adds a status. It appears both on the map and as a column on the board.
  • Statuses are deleted on the board itself. On the map, you only arrange and connect them.
  • You can add bend points to an arrow: click the arrow to add a point, then drag the point. Clicking a point removes it.
  • The question mark button at the bottom of the panel opens a short help on the map.
The board workflow on a phone

On a phone, there is no panel on the left. The gear button on top of the map opens the “Board workflow” window with the “Create a status” button, the “Activate the workflow” switch and “Help”. To move a status card, hold your finger on it for a moment. Drag an empty area to move the map and pinch to zoom. If you zoom far out, the points on the cards stop responding to your finger: zoom in to draw an arrow. See “The workflow map on a phone or tablet” for more about gestures.

If your Business plan has ended

The map stays where it is and is view-only: you can't change or delete transitions. The board stops restricting moves by it, and the switch shows “Off”. Once you pay for Business again, the map works as it was drawn. See “Workflows and plans”.

On the website: Cross-team processes in Fluo: linked boards without code