A Kanban board is an alternative way of working with tickets in the Tickets application. Instead of displaying tickets in one list, the board places them as cards in columns. The columns are defined by a ticket field or by the activities of a process.

Kanban views are listed in the sidebar under the Kanban group. The tickets on a board are still subject to the configured ticket filter and to the current user's permissions.

The structure of a board is configured in the Kanban View Settings. The appearance of cards is configured separately in the Kanban Layout Settings.

Click a card to select its ticket. Use the available selection controls to select multiple tickets or the tickets in a column. Double-click a card to open the ticket.

Actions available for a selection are shown in the toolbar. When several tickets are selected, Move to lane moves them to a common target column only if every selected ticket can be moved without an additional action or additional required information.

The sorting menu above the board provides ticket fields and two manual sorting modes:

• Manual (all Users): Dragging a card to another position stores an order shared by all users of the Kanban view.
• Manual (only me): Dragging a card to another position stores a personal order for the current user.
• Ticket field: Cards are sorted by the selected field in ascending or descending order. Manual reordering inside a column is not available with this type of sorting.

The selected sorting is stored for the current Kanban view.

Drag a card to an allowed target column to change the ticket value represented by that column. The available targets are determined separately for each ticket.

A target may be unavailable when the grouping field cannot be edited, the ticket is closed and its fields may not be changed, a required status action does not exist, or the current user lacks the necessary permission. For process-based boards, a target activity must be reachable from the ticket's current activity.

Moving a ticket may open an action dialog or a dialog for required fields. If the Kanban view is configured to skip the action dialog, the action is executed directly only when it does not require information that must be entered by the user.

When a move changes the ticket so that it no longer matches the search phrase, dependent view, visible columns, or the user's permissions, the card disappears from the board after the move.

A plus button is displayed in a column when the current user may create tickets there. The button opens the form configured for the Kanban view, or the standard New Ticket dialog when no form is configured.

The new ticket is assigned to the column from which it was created. This column value takes precedence even if the creation form initially contains another value. On a status board, tickets can be created only in the initial request status. On a process board, creation is available only for a valid start activity.

Each column displays the total number of tickets it contains. Tickets are loaded in blocks as a column is scrolled. Therefore, the displayed total can be greater than the number of cards currently loaded in the browser.

Drag the handle at the right edge of a column to change the width used for the current Kanban layout. Use Reset column widths in the board's options menu to restore the default width.

The board shows the intersection of:

• the optional search phrase,
• the optional dependent ticket view,
• the columns selected in the Kanban View Settings, and
• the tickets the current user is permitted to read.

Kanban does not bypass ticket permissions. A column can therefore show zero tickets for one user even though other users see tickets in it. Moving a ticket to such a column can make the ticket disappear for the user who moved it.

Removing a column from Visible Contents also excludes that column's tickets from the Kanban view. A search phrase can have the same effect. For example, a column may remain visible while the search phrase excludes all tickets whose grouping field has that column's value; tickets moved there then leave the current result.

On a field-based board, every column represents a selectable value of one ticket field. Moving a card changes that field. Depending on the field, tickets without an applicable value appear in an Unassigned column.

On a process-based board, columns represent process activities. Moving a card performs the transition to the target activity. Related tickets in the same process can be highlighted together on the board.