Creating and Editing Kanban Views

The Kanban Views tab in the View Settings lists every Kanban view available to the current user. Visible entries appear in the sidebar of the Tickets application under the Kanban group.

Use Add New Kanban View to create a board. Editable entries provide actions for editing and removing the view. Visibility controls determine whether an available board is shown in the sidebar, and the entries can be reordered in the list.

Supporters and users with permission to define templates can create Kanban views. Sharing a view requires permission to define templates and, when groups are selected, access to user and group management.

For instructions on using a configured board, see Kanban Boards. Card appearance is configured in the Kanban Layout Settings.

The filter determines which tickets can appear on the board.

• Search Phrase: Optionally restricts tickets using the ticket search syntax. An empty search phrase does not add a search restriction.
• Dependent on view: Optionally restricts the result to tickets contained in the selected ticket view. When both a search phrase and a dependent view are set, a ticket must match both conditions. Kanban views cannot be selected as the dependency.

A Kanban view does not offer a separate Grouping setting in the ticket filter. Its columns are configured using the Kanban Grouping Field described below.

• Name: Required name displayed in the sidebar and in the board header.
• Description: Optional explanation shown with the Kanban view in the settings.
• Icon: Optional image used for the view. Resetting it restores the Kanban icon.

The Kanban Grouping Field determines the source of the board columns:

• Field-Based: Select an available single-value selection field of a ticket. Each selectable value becomes a column. Moving a card updates this field. Multi-selection fields are not available. Status is supported and uses the available ticket actions to determine allowed target columns.
• Process-Based: Select an available process. Its activities become columns. A ticket can be moved only to an activity reachable by an available transition.

The available choices are provided by the installed Kanban providers and plugins. Changing the grouping field resets Visible Contents to the columns of the newly selected field or process.

This option is available for process-based boards. When enabled, activities with the same name are displayed as one column. Changing the option resets Visible Contents to the corresponding process columns.

Moving a ticket can require a ticket action. Enable this option to execute the required action directly whenever it can run without user input. If required fields, text, effort, or other input must be supplied, the dialog is still displayed.

Visible Contents defines the columns included in this Kanban view. Columns can be:

• reordered using drag and drop or the arrow buttons,
• assigned an individual background color,
• removed from the board,
• added again from the available values or activities, and
• restored to the provider's default using Reset.

For process columns, the activity description and process grouping are displayed when available.

Removing a column excludes its tickets from the Kanban view's search result; it does not merely hide the column in the browser. Some grouping fields provide an Unassigned column for tickets without an applicable value. Fields such as Priority do not provide such a column.

This option is shown when ticket creation forms are available. Select a form to use when a ticket is created from a column header, or select None to use the standard New Ticket dialog.

The selected form must create tickets and be available to the current user. The target column selected by the plus button is applied to the newly created ticket.

The Card Highlight settings color cards according to a ticket field. Select No highlight to disable this feature.

• Selection field: Assign a color to any of the field's fixed selectable values.
• Number field: Create ordered rules using Equals, Greater than, Greater or equals, Lesser than, or Less or equals.
• String field: Create ordered rules for equality, inequality, containing text, not containing text, starting or ending with text, and comparisons of the text length.

Rules can be reordered. They are evaluated from top to bottom, and the first matching rule supplies the card color. Fields with multiple values and fields without a supported stable value are not offered.

Users with permission to define templates can share a Kanban view with selected user groups. Members of those groups can then make the shared view visible in their sidebar.

The creator can cancel sharing. Removing all selected groups also removes access for users who received the view only through those groups. Sharing a view does not grant access to tickets; every user continues to see only tickets permitted by the ticket authorization rules.