Documentation

Boards

A board is one place that holds its tickets, its intake forms and its settings. This page explains where your boards live, how to create, duplicate and delete one, and who can see which.

Where boards live

Every board you can see is a row under Communications → Tickets in the left-hand menu. There is no boards overview page — the sidebar is the list. The Tickets entry only appears at all once you can see at least one board.

The old address /dashboard/settings/boards no longer exists and does not forward anywhere. Opening the bare address /dashboard/tickets takes you to the first board you can see, or to the dashboard home if you have none.

Creating a board

＋ New board is the last row of the Tickets list. It creates a board straight away, with a default name and a single starting column, and opens its Settings tab so you can rename it and pick its type.

Creating a board needs the Board management right (Tickets.Boards). Without it the row is not shown.

What a board is

One place with three tabs, each with its own address so it can be bookmarked:

  • Tickets — the kanban board. See Board View.
  • Forms — the intake forms that create tickets here. Shown only with the Forms right.
  • Settings — name, type, roadmap widgets and the danger zone. Shown only with Board management. See Board Settings.

A member without a right does not see the tab at all, rather than clicking it and being refused.

Board types

The type is set on the board's Settings tab and decides how the board behaves:

  • Bug — technical issue tracking
  • Feature Request — can be published as a public roadmap on a chat widget
  • Custom — a flexible board for any other purpose

A board created by an import is always Custom, so if you imported a public roadmap, change its type on the Settings tab before you try to share it.

Intake forms

Forms belong to the board they feed and are built on that board's Forms tab. The old organisation-wide Automation → Forms list is gone, and a form can no longer exist without a board attached.

Duplicating a board

Duplicate this board sits in the board toolbar's export/import menu — the two-arrow button at the top of the kanban. It copies the board as "name (copy)" with its columns, labels and tickets, and opens the copy. The copy is created as a Custom board whatever the original's type was, so set the type again on its Settings tab if you were duplicating a roadmap.

Duplicating requires the Board management right, but the menu entry is not hidden from members who lack it. A member with only the Tickets right who clicks it gets an error message instead of a copy.

Exporting and importing

The same two-arrow menu holds Export this board…, Copy board for AI and Import into this board…. Formats, limits and exactly what does and doesn't come across are covered in Importing and exporting boards.

Labels

Labels… in the same menu opens the label manager for this board. Labels belong to one board and are not shared between boards; the full description is on Board View.

Deleting a board

Deleting happens in the danger zone at the bottom of the board's own Settings tab. The confirmation counts the real tickets and intake forms first, warns that anyone using one of those forms in a widget stops being able to submit, and refuses to go ahead until you type the board's name.

The two boards your account was created with are marked as defaults and cannot be deleted.

Deletion runs on the server, so colleagues who have the board open see its tickets vanish immediately — the board's own row stays in their sidebar until they reload the page. The deletion is written to your audit log.

Board deletion is permanent. It removes every ticket on the board and every intake form that feeds it, and there is no undo.

Who can see which board

Access is granted board by board, so two colleagues can hold the same Tickets right and still see different boards. An organisation owner bypasses that and sees every board; an administrator does not. Whoever creates a board is granted access to it automatically. The switches are on the team screen, reached from the profile menu behind your avatar → Manage team → expand the member → Board access.

Board Access and Permissions

The three rights that control tickets, what each one hides on screen, and how per-board access is granted.

Organising your boards

Managing multiple products

  • Use separate boards for different products or services
  • Create feature request boards that can be made public for customer feedback
  • Maintain bug report boards for technical issue tracking

Form strategy

  • Attach multiple forms to a single board for different submission scenarios
  • Use forms to collect different types of information (bug reports, feature requests, general feedback)
  • Configure forms with appropriate fields, validation, and automated responses

Best practices

  • Consistent Naming: Use clear, descriptive board names that indicate their purpose — the name is what your colleagues see in the sidebar
  • Appropriate Types: Choose the right board type based on the primary use case
  • Form Organization: Keep forms focused and avoid creating too many forms per board
  • Access Control: Grant board access deliberately, since it is separate from the Tickets right