Fluo

How to set up the ticket form

Updated:

The ticket form in a Fluo service desk is the set of fields the ticket author fills in. You set it up separately for each desk.

How to set up the form

  1. Open the desk settings and click “Set up the desk task form” in the “Desk settings” block. The “Desk task form” window opens.
  2. On the left is the “Ticket form”: this is how the author sees it. The “Title” field is always there and can't be removed. On the right is the “Field storage”: project fields that aren't in the form. Each column scrolls on its own.
  3. Drag a field from the storage to the form or just click it. Change the order of fields in the form by dragging.
  4. Click a field in the form. Its “In the desk only” settings open under the storage: “Name in the desk”, “Width in the desk” and “Required in the desk”.
  5. Changes save automatically three seconds after your last edit. While they're being saved, the bottom of the window shows “Saving”. Click “Close”.
The Desk settings block in the settings window: the Set up the desk task form button is numbered 1
The Desk task form window: the Ticket form column is numbered 2, the Field storage 3, and the settings of the selected field In the desk only 4
SettingOptions
“Name in the desk”Your own field name for this desk. If empty, the field has its project name. The name on boards doesn't change
“Width in the desk”“As in the project”, “Half width”, “Full width”
“Required in the desk”“As in the project”, “Optional”, “Required”

The “Default” button above the form restores the original set: “Description”, “Priority” and “Deadline”.

How to remove a field from the form

There are three ways, and each puts the field back into the storage:

  • point to the field in the form and click the “Remove from the form” cross in its top right corner;
  • select the field and click “Remove from the form” at the bottom of its settings;
  • drag the field to the storage. While you're dragging a field out of the form, the storage is highlighted with a frame and the hint “Drag a field here to take it out of the ticket form.”
Animation: the Priority field is dragged from the form to the storage, which is highlighted with a frame and a hint; then a click on the field in the storage puts it back into the form

The name, width and required setting you gave the field in the desk are kept: if you put the field back into the form, they stay the same.

The “Task type” field

A project can have task types, such as “Question” or “Bug”, and each type has its own route across the boards. The “Task type” field in the form sets the ticket's type and with it the route: a ticket with a type is sent along the desk's connections in that type's route, and a ticket without a type along the connections of the “No type” route. See “Task types: create, choose, change” for task types and “One desk connection or several” for desk connections in routes.

The “Task type” field is the first one in the storage. You put it in the form like any other field, in any place.

  1. Drag “Task type” to the form and click it.
  2. In its settings, choose the width: “Half width” or “Full width”.
  3. Choose “Optional” or “Required”. The field can't be renamed.
  4. Turn “Allow desk requesters to choose the task type” on or off.
The Task type field in the desk form: the field with the crossed-out eye icon and the tooltip Desk requesters do not see this field is numbered 1, the width 2, required 3, and the Allow desk requesters to choose the task type toggle, turned off, 4

The project team always sees the field and can set any type. If the field is in the storage, the team sees it at the end of the form.

Requesters can't choose the type

The field in the form only marks the place where project members see it. Requesters, that is, people invited to the desk and ticket authors, don't see the field. In the editor, the field shows a crossed-out eye icon with the tooltip “Desk requesters do not see this field. Only project members see it.” If the team has set a type for a ticket, the requester sees it in their ticket but can't change it.

Requesters can choose the type

A requester chooses the type when creating a ticket and can change it in their own tickets. The “Types for requesters” list appears below in the field settings. By default, “All types” is checked: the requester chooses from all of the project's types. Check specific types to offer only those. Requesters can't create new types.

The Task type field settings: the Allow desk requesters to choose the task type toggle is on, and below it the Types for requesters list with Question and Bug checked

This is the same setting as the “Allow desk requesters to choose the task type” toggle in the main desk settings, see “Desk settings”. Turn it on in one place, and it's on in the other. If you move the “Task type” field to the storage, requesters can no longer choose the type.

The “Task type” field in the form and the type choice for requesters work on Pro and Business. On Free and Free Team, the field disappears for requesters, and the toggle in the desk settings has a lock with the tooltip “Desk requesters choose the task type on Pro and Business”. The project team sets the type on any plan. The field settings are kept and come back once the plan is paid again.

The project has no task types yet

You can still put the field in the form, and its settings show the warning “The project has no task types yet”. A project member who can change the project workflow creates the first type right from the field with “New type” in the list. Creating types is available on Pro and Business. Requesters only choose from existing types.

Which fields you can add

  • System task fields, for example “Description”, “Priority” and “Deadline”.
  • “Task type”.
  • Custom project fields, for example “App version”.
  • Tags, epic and status can't be added to a desk form.

A new project field doesn't get into the form by itself, it appears in the storage. A field turned off in the project isn't shown in the desk either.

Where the form is used

Everyone who creates tickets on the desk page in Fluo sees the form: the team, people invited to the desk and users with the public link. Their button is “Create a task”.

The widget on your website doesn't use this form. It has its own set of fields: “Subject”, “Details”, “Your name” and “Email”. The widget has no task type, so a ticket from the widget arrives without a type. The draft for the ticket description is set in the desk settings, in the “Task description template” field, and it goes into the widget too. See “Desk settings”.

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