Fluo

Task types: create, choose, change

Updated:

In Fluo, you create task types on the project's Workflow page or in the “Task type” field of a task. You can change a task's type at any time, and the task then follows the new type's route.

What task types and routes are is explained in “Project workflow: task routes and task types”.

How to create a type on the Workflow page

  1. Open the project and click “Workflow” in the header.
  2. In the top-left corner of the map, click the “Route: …” button.
  3. At the bottom of the list, click “Task type”.
  4. In the “Name” field, enter the type name, for example “Supply contract”. The icon is picked from the name automatically.
  5. In the “Icon and color” block, choose another icon and color if you like. The route lines on the map are drawn in this color.
  6. In the “Copy the route from” field, leave “Start from scratch” or choose the route whose links you want to take: “No type (default)” or another type. The list shows only routes that already have links.
  7. Click “Create the type”.
The Workflow page: the Route: No type button is numbered 2, below it the open Routes of task types list with No type (default) and the project's types, the Task type button at the bottom of the list 3, and the drag handle of the first type is outlined
The New task type window: the Name field with “Supply contract” is numbered 4, the Icon and color block 5, the Copy the route from field set to Start from scratch 6, and the Create the type button 7

Fluo opens the new type's route on the map. If you started from scratch, the type has no links yet: draw them as described in “How to connect columns of different boards”. If you copied a route, the new type has its own copy of the links and rules, and changes to it don't affect the source. Changed your mind? Click “Undo” in the notification at the bottom of the screen.

How to create a type from the task window

The “Task type” field appears in the task creation window and in the task window once the project has at least one type. The project's first type is created on the Workflow page.

  1. Click the “Task type” field.
  2. Below the list, click “New type”. If you've already typed something in the list's search, it becomes the type name.
  3. The “New task type” window opens on top of the task window. Enter a name, choose an icon and color, and click “Create the type”.

The new type is selected in the field right away. If the project has routes with links, the window also has the “Copy the route from” field. Otherwise the type is created without a route, and a task of this type won't go anywhere along links until you draw them.

How to edit, copy or delete a type

  1. On the Workflow page, click the “Route: …” button and choose a type.
  2. Click the “⋮” button next to it.
  3. Choose an action.
The Workflow page with the Feature route selected: the ⋮ button next to the route button is numbered 2, and the open menu with Edit, Copy the route and Delete the type… 3
  • “Edit” opens the “Edit the task type” window. A new icon and color apply as soon as you pick them. A new name is saved with the “Save” button.
  • “Copy the route” creates a new type “… (copy)” with a copy of the links, rules and map layout. Nodes hidden from the map of the original route are hidden in the copy too. The name field opens for editing right away: enter a new name and press Enter. From then on it's a separate route.
  • “Delete the type…” opens the delete window, described in the next section.

For “No type”, the menu has only “Copy the route”. This route can't be renamed or deleted, and its copy is named “New task type”.

What happens to tasks when you delete a type

  1. Choose the type, click “⋮” and select “Delete the type…”.
  2. In the “Delete the type ‘…’?” window, select which type the tasks get instead: “No type” (selected in advance) or another type of the project. If the type has tasks in progress, the window shows how many.
  3. Click “Delete the type”.
The Delete the type “Feature”? window: the number of tasks in progress and the replacement options, No type and the project's other types, are numbered 2, and the Delete the type button 3

After deleting:

  • tasks stay in their columns and get the type you chose, closed tasks included;
  • open checks added by the deleted type's links are dropped;
  • in status automations and link rules, the “Change the task type” action that set the deleted type now sets the replacement, and if you chose “No type”, the action is turned off;
  • task templates with this type are left without a type, and a task created from such a template has no type;
  • rows with this type disappear from the “Task types at the exit” tables of connectors;
  • in the list of types that service desk requesters can choose, the deleted type is replaced with the one you chose. If the list becomes empty, requesters can no longer choose a type.

How to change the order of types

  1. On the Workflow page, click the “Route: …” button.
  2. Hover over a type: a handle with dots appears on the right of its row. On a phone it is always visible.
  3. Drag the type by the handle up or down.

The order is shared by the whole project. Types appear in the same order in the “Task type” field, in the board filter and in templates. “No type” always comes first and can't be dragged.

How to choose the type of a new task

  1. Open the task creation window, for example with “Add a task” in a board column.
  2. Click the “Task type” field.
  3. Choose a type.
The task creation window on the Development board: the Task type field is numbered 2 and the open list 3. The list starts with the types whose route passes through the board, followed by No type, All project types and New type

By default a new task has no type, and the window doesn't remember your last choice. Once a type is selected, the task's path along that type's route appears above the fields.

The order of options depends on where you create the task:

  • on a board, the types whose route passes through this board come first, then “No type”, and at the very bottom the “All project types” item with the other types. Click it to open a nested list. If no route passes through the board, the list shows “No type” and all types in a row;
  • without a board, “No type” comes first, followed by all project types in order.

If the list has more than six options, a search line appears above it. It searches all project types, including the nested ones.

A task template can set the type too, see “Task templates”.

Where you can see the task type

In the task window:

  1. Above the title is the task's path. These are the boards of its type's route in order: the ones already passed have a check mark, the current one has a dot, and the next ones follow. If a board appears in the path twice, its column is shown next to it. A long path scrolls sideways. If the task is somewhere its type has no links from, the path is replaced with a note that this type has no further links from here.
  2. The “Task type” field with the type's icon in its color.
The window of a Feature task: the path above the title (Design with a check mark, Development with a dot, then Testing and Release) is numbered 1, and the Task type field 2

A task with no type and a closed task have no path above the title.

On a card, the type comes first in the line under the title: the icon in the type's color and the name. In the “Minimal” and “Icons” card views only the icon is shown, and hovering over it shows “Type: …”. A task with no type has nothing extra on its card.

The Habit sync task card on the Development board: the icon and name of the Feature type come first in the line under the title and are outlined

To show only tasks of one type on a board:

  1. In the board header, click the funnel button, “Filters”.
  2. In the “Type” list, check the types you need or “No type”. You can check several.
The Development board: the Filters button in the header is numbered 1, and the Type list in the filter panel 2

The “Type” filter is on the board when the project has at least one type. The other filters are described in “Filters and search on a board”.

How to change the type of a task

  1. Open the task.
  2. Click the “Task type” field and choose another type or “No type”.

You don't need to click “Save”: the type changes at once. A notification appears at the bottom of the screen, “Next the task will follow the ‘…’ route.”, with an “Undo” button. If you choose “No type”, the notification says “Next the task will follow the current links of the project.”

Animation: in the task window, the Task type field is clicked and Bug is chosen, a notification “Next the task will follow the ‘Bug’ route.” with an Undo button appears at the bottom, Undo is clicked and the type goes back

The type can also change without a manual choice:

What happens after the type changes

  • The task stays in the same column. Status automations don't run again when the type changes.
  • From now on the task follows the links of the new type. Its path starts from this moment: returns count only by new moves, and waiting after a return is cleared.
  • Open checks added by the old type's links that the new type doesn't have are dropped and marked “dropped when the task type changed”. Column checks stay, because they apply to tasks of any type.
  • If the new type has a link from the current column with “The task moves on by itself” turned on and nothing holds the task, the task moves along it right away.
  • The task history gets a “Task type changed” entry.

The type when a task moves to another project

Types belong to a project. If you move a task to another project (to one of its boards or its Inbox, one by one or in bulk), Fluo looks there for a type with the same name; letter case doesn't matter. If there is one, the task gets it and follows its route from then on. If there isn't, the task arrives with “No type”. Such a move doesn't create a copy of the type.

There are two exceptions:

  • with a connector, the type at the exit is set by the “Task types at the exit” table. If the table has no row for the task's type, the task arrives with “No type”, even if the other project has a type with the same name. See “Connectors: passing tasks between projects”;
  • if whole boards are moved to another project (select them on the workflow map and choose “Move to another project”), tasks on these boards keep their type. Fluo looks for a type with the same name in the target project and creates an identical one if there isn't one.

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