Working With Views and Feeds → Using Kanban Boards → Creating Kanban Boards
You can create Kanban boards in the global context (All) or for each application or application group. You are the owner of each Kanban board you create, but you can share the board with co-owners, collaborators, and viewers. For details on the responsibilities of users who share a Kanban board, refer to Sharing a View With Other Users.
To create a Kanban board:
Enter the name that will appear above the column.
Enter an abbreviation that appears when the column is collapsed. Short names are limited to four characters or less.
Provide a description for the column.
Select this check box on one of the columns to designate it as the default for items with a status value that is not mapped to one of the columns.
Set the work in progress (WIP) limit for the column. The WIP limit acts as a threshold for the number of items that should be added to a column. When the WIP limit for a column is exceeded, the column heading displays the overage to notify the user who is viewing the board.
Add columns for each phase or stage of your process. In the list of columns, hover over a column and click Add sub-column to add more granular stages. Click the minus icon to remove a column, if necessary.
Use the up and down arrows to re-order the columns. Columns at the top of the list appear on the left side of the Kanban board.
Select a field with values that you want to associate with this column. Note that you can map one field per application—you can change this field later, but any mappings you have defined will be lost if you change it.
Note that you can map Single-Relational fields to columns; however, the Single-Relational must point to an auxiliary table. For example, you can create a Kanban board in which each column represents a different scrum team or Agile sprint (assuming you have auxiliary tables that stores scrum teams and Agile sprints.)
The current column is selected in this drop-down list, but you can select another column and change the mapping for it as well. This enables you to define all of the column mappings at once without having to close the dialog box. Note that if you add sub-columns, you will map values to each sub-column (not the parent column).
For example, for items with State field values like Backlog, Assigned, Researching, In Development, Assigned to QA, and Closed, you could create the following mapping:
In this example, the In Progress column contains two sub-columns (Research and Development). The Researching and In Development state values that are part of the overall active development phase ("In Progress") are mapped to these sub-columns.
If you need to change any mappings, you can click the pencil icon next to the mapped field or you can click the Map Values button.
Copyright © 2013–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.