Fluo

One desk connection or several

Updated:

In Fluo, you draw one connection or several from a service desk to board columns. With several connections, you pick the column for a ticket by hand, and with one, the desk can send tickets itself.

You draw connections on the project's “Workflow” map, as described in “How to create a service desk and connect it to a board”. On the map, a connection is a line from the desk card to a board status. How many connections are allowed is set by the “Desk connection type” block in the desk settings.

The Workflow map: the desk with two lines to different boards is numbered 1, and the desk with one line 2
  1. A desk with several connections: lines go from it to different columns.
  2. A desk with one connection.

Desk connections and task type routes

A project can have several task types, such as “Question” and “Bug”. Each type has its own route across the boards, and tasks without a type follow the “No type” route. Desk connections belong to a route, and each route has its own. See “Project workflow: task routes and task types” for routes.

  • A ticket without a type is sent along the desk's connections in the “No type” route.
  • A ticket with a type is sent along the desk's connections in its type's route. If that route has no connection from the desk, the ticket card has no arrow, and the ticket waits in the queue.
  • Change a ticket's type, and the “Move task to” menu shows the columns of the desk's connections in the new route.

Tickets from the widget arrive without a type. The type is chosen by the project team, and by requesters only if the desk settings allow it, on Pro and Business. See “How to set up the ticket form”.

Several connections

Every new desk gets the “Multiple desk connections with statuses” type. You can draw connections from the desk to columns of different boards, for example to “Support” for questions and to “Bugs” for failures. A ticket waits in the queue until someone picks a column for it in the “Move task to” menu.

This type suits you when tickets vary and a person should decide who handles them. It works on Pro and Business. On other plans, there's a lock next to the block name.

One connection

The “One desk connection in each route” type allows only one connection per route. You can't draw a second line from the desk in the same route, and Fluo says “This desk can only have one connection with a board status”. In another type's route, the desk can have a connection of its own.

Such a desk can have “Automatically send task to board upon creation” turned on. Then every new ticket goes straight to the column the desk's connection leads to in the ticket type's route, and doesn't wait in the queue. This works both for tickets from the widget and for those created in Fluo. If the ticket type's route has no connection from the desk, the ticket waits in the queue. Without this toggle, tickets wait in the queue as usual too.

One connection with automatic sending suits you when all tickets go to one place: partner requests, internal requests to a department.

How to change the connection type

  1. Open the desk settings: the “Desk settings” gear on the desk page.
  2. In the “Desk connection type” block, choose a type.
  3. For the one-connection type, turn on “Automatically send task to board upon creation” if tickets should go to the board by themselves.
  4. Click “Save”.
The Desk connection type block in the desk settings: the One desk connection in each route choice is numbered 2 and the Automatically send task to board upon creation toggle 3

The automatic sending toggle works only with one connection. With the “Multiple desk connections with statuses” type, it's off and can't be clicked.

Who sends tickets along connections

The project team can always do this. People invited to the desk need the “Allow desk participants to move tasks to boards themselves” permission, and they choose a column only from the desk's connections. Ticket authors from the widget don't get this button.

On Free and Free Team, the “Workflow” map is view-only, and you can't draw new connections on it.

On the website: Fluo service desk: client requests straight to the board, site widget