Fluo

Project workflow: task routes and task types

Updated:

In Fluo, each task type has its own route: a set of links between the columns of the project's boards. A task follows the route of its type, and a task without a type follows the “No type” route.

Task type and route

A task type tells what kind of work it is: “Contract”, “Claim”, “Bug”. A type has a name, an icon and a color. Types belong to a project, and each project has its own list.

A route is the set of a type's links on the workflow map. A link goes from a column of one board to a column of another board or of the same board. It can also go from a service desk to a column, or between a column and a connector. A task of the “Bug” type follows the links of the “Bug” route and doesn't see the links of other types.

“No type” is the default route. It holds all the links the project had before task types appeared, and they work as before. A new task is created with no type unless you choose one in the “Task type” field. How to create a type and give it to a task is described in “Task types: create, choose, change”.

Routes don't overlap

Each link belongs to exactly one route. Other routes don't have it, either on the map or when a task is moved. This applies to links between columns, links from a service desk and links with a connector.

If two types need the same path, copy the route: the type menu has a “Copy the route” item. The copy gets its own links with the same rules. After that you edit it separately, and the source doesn't change.

Each route has its own map layout. If you move a board on a type's map, it stays in place on the maps of other routes. Groups on the map are also separate for each route.

The place and the road

Conditions and actions can belong to a column or to a link.

When a task is moved along a link, the conditions of the column and of the link add up: both have to be met. If the column and the link set a different assignee, deadline or type, the link wins.

Moving isn't forbidden, but conditions hold the task

A route suggests the way. The arrow on a task card offers the columns of its type's route. A link with “The task moves on by itself” turned on moves the task without anyone's help as soon as nothing holds it. See “How a task moves along its route”.

A route doesn't set a hard ban. You can drag a task to any column of the board and to any board you have access to, even if there is no link there. But conditions and checks always hold a task: until they are met, the task won't move, and there is no way around them. What exactly stops a task is explained in “Conditions and checks: what holds a task”, and what to do if a task isn't moving is in “Why a task isn't transferred”.

The Workflow page

Routes are drawn on the Workflow page of an extended project. Open the project and click “Workflow” in the header. A simple single-board project has no such page. The difference is described in “Simple and extended projects: how a project grows”.

The Workflow page of the Aurora project with the Feature route: the Route: Feature button in the top-left corner of the map is numbered 1, the Development board with its columns 2, and the label of the link from Development to Testing 3
  1. The “Route: …” button in the top-left corner of the map. It shows the icon and name of the selected route. Click it to open the “Routes of task types” list: “No type (default)” with a dotted circle comes first, then the project's types. The selected route is filled with color. Next to the button is the “⋮” button with actions for the type.
  2. The map of the selected route. It shows boards with their columns, service desks, connectors, forks, groups and only the links that belong to this route. Lines between columns of a type's route are drawn in the type's color. Boards, service desks and connectors that the route doesn’t pass through can be hidden from its map, see “Bend points, groups and map tools”.
  3. A link. Its label sits in the middle of the line. A new link gets the names of its two columns, for example “Development / Testing”, and a link whose label was cleared says “Next”. A paper plane icon means the task moves on by itself, a lightning bolt means the link has its own rules.

To the left of the map is a side panel with buttons that add boards, service desks, connectors and groups to the map. The map help is at the bottom of the panel.

A new link goes into the route that is selected right now. While a route has no links, a hint at the bottom of the map says “Draw a link between nodes of the map: columns, service desks or connectors. It goes into the route “…”.” The hint goes away as soon as the route has any link, including one from a service desk or to a connector. How to draw links is described in “How to connect columns of different boards”.

To see another route, click the “Route: …” button and choose a type. The map is redrawn at once. The page remembers the last route you selected in the project, and a link to the page opens the route that was on screen.

Animation: on the Workflow page, the Route: Feature button is clicked, Bug is chosen in the Routes of task types list and the map shows the bug links, then No type is chosen the same way

Example

The Aurora project has several task types, among them “Feature” and “Bug”. A “Feature” task goes from Design to Development, then to Testing and Release. A “Bug” task starts in the “Bugs found” column of the Testing board, goes to Development and comes back for testing. A link from “Development / Ready for testing” to “Testing / Queue” exists in both routes, but these are two different links. For bugs you can turn on “The task moves on by itself”, keep manual moves for features, and one won't interfere with the other.

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