Starting from version 4.5, Urban Turtle allows user to define multiple board from the web interface. Different boards representing different workflows can be assigned to an iteration. This allows team that have multiple responsibilities or that have sub teams that are working on the same project that use different workflows to get more flexibility
Creating a New Board
Boards are created and managed from the Configuration/custom boards tab. To create a new board, click on the Create a new board link. A toolbar allowing usual basic operations appears below.
The name of the board must be defined. This will allow the board to be identified when it has to be assigned to an iteration.
Adding a column
Adding a column is a simple procedure done by clicking on the New column button. Columns must have a unique name.
WIP limits can be set to show visual cues when the number of total work items in a column is over or under a particular limit. The WIP limits are disabled when both the minimum and maximum fields are set to 0. Once multiple columns have been defined, it is possible to reorder them using drag and drop. Adding a new column should display a widget like this one:
Mapping states to columns
For Urban Turtle to dispatch the work items in the proper columns, each state for each work item types has to be mapped. Unlike the sprint backlog, a single state can be mapped to multiple columns allowing for more flexibility. If a work item is moved to a column which is mapped to the same state, it will not switch state but will retain its position in the board. States are different for each work item types, thus each type will have to be configured individually for each column by using the drop down menus. The next screenshot shows an example of a configuration:
It can be noticed that the Task work item type maps the In Progress state to both the In Progress and Ready To Test columns. Assuming a normal progression, it will only switch states when transitioning from column 1 to column 2 (from To Do to In Progress) and from column 3 to column 4 (from In Progress to Done).
The changes to the board's configuration must then be saved by clicking on the Save Configuration button.
Assigning a Board to an Iteration
Board assignation is done through the iteration's configuration page that is under the Configuration/iterations tab. If the Product Backlog add-on is activated, iteration configuration can also be reached by clicking on the circled I icon next to the iteration All the iterations defined for the team are listed. Clicking on the pen icon brings a dialog box which contains a drop down list that allows to choose the board to assign to that iteration. The list contains all the board previously defined, represented by their respective names.
Once a board has been assigned an iteration, all its children inherit that board unless specified otherwise.
Boards can be edited and deleted from the custom boards tab. To do so, one has to select the board that has to be edited from the Select drop down list. Boards can then have column added and configured in the same way that is described above.