Taskboard

The taskboard allows developers to keep track of the status of their work. Accessible from the menu, the taskboard opens as a floating document by default, as developers will often keep the taskboard opened and visible while working in the various modelers.

Every leaf-level iteration that is currently active is available as a taskboard by default. This is determined by the start- and end date of the iteration. Multiple taskboards can be active at the same time. This is useful when working with multiple teams.

A prefilter can be turned off to show the taskboards for past and future iterations.

A taskboard

Lanes

The configuration of lanes in the taskboard is determined by the work status.

Each individual work status can be configured to correspond to a certain lane in by specifying the Taskboard sequence no. When left empty, work with this status will not show up in the taskboard. The taskboards require a minimum of 2 lanes to function and can have up to 5 lanes.

Multiple work statuses can use the same Taskboard sequence no. This way, work with multiple statuses can be placed in the same lane.

An example work status configuration. Six of the statuses are included in 4 taskboard lanes.

Work details

The zoom button at the bottom of each lane can be used to further inspect the selected work in this lane. This will open a new floating document or will reuse an earlier opened work document.

Attachments, the work log, the linked requirement, business process, feature and iteration are all available here.

Drag-drop

The developer can drag-drop work from one lane to another to change the status. When a lane represents more than 1 status, the developer will be asked to provide the new status.