Board module

Contents: 1 About the Board module 2 Board hierarchy 3 Main features 4 Constraints

Contents: 1 About the Board module 2 Board hierarchy 3 Main features 4 Constraints

About the Board module

The Board module is a powerful tool whose primary purpose is to visualize and highlight new feature delivery dates and cross-team dependencies. However, if you work in non-agile teams, you can plan your tasks and coordinate the work you plan with the other teams.

The Board module is very helpful during planning sessions (such as Program Increment (PI) Planning or Iteration planning) as it can show capacities across different teams. But there is much more the Board module can help you with. For example, it can boost the way you monitor timebox execution thanks to its built-in reporting features and various progress bars that will help you and your team stay on track.

The Board module also incorporates a timeline that shows important events or milestones. Plus, you can customize the task cards by using the card view creator.

The Board module, The Essentials option chosen

Board hierarchy

The Board module utilizes the concept of the box hierarchy, which needs to be configured first in the Overview module. You can zoom in on three levels of boxes, for example:

Program
Program Increment
Iteration

If you create multiple sub-boxes, the board can display up to two levels.

The data on the Board can be displayed at one or two levels, such as the iteration level only or the program increment and iteration levels.

Main features

The table below describes the Board's main features:

Feature	Description

Feature	Description
+Add task	Use this option to add tasks by: Creating new tasks in the host platform (the host platform is the Jira instance you are currently using) Creating basic tasks Use this option to access the scope definition page: Manage scope definition
Swimlane picker	Display or hide swimlanes of various types.
Timebox reports	Generate instant reports using charts for each timebox.
View	Adjust the way cards are displayed or quickly collapse all the team swim lanes to get an overview of your teams' progress. View settings include the following features: Layout Compact Regular Wide Totals Type None Work progress Capacity allocation Aggregate by Story points Original Estimates Remaining Estimates Task warnings Show objectives
Dependencies	Expand or collapse the dependencies for better visibility.
Dependencies / Browse dependencies	Display different dependency types and resolve conflicts. Click Browse dependencies to open dependencies in the Infobar panel. Incorrect dependencies (red) - target tasks are planned in previous timeboxes. Dependencies at risk (orange) - target tasks are planned in the same timeboxes. Correct dependencies (green) - target tasks are planned in next timeboxes. Dependencies out of view (purple) - target tasks are out of view.
Export	To unlock the export features, install the BigTemplate App from the Atlassian Marketplace. PDF image export requires NodeJS installation. You can Export the Board module data using the "Export" button:
Inline editable field	You can inline edit the text and number fields both on a task card and within the backlog. Inline edit the Summary field: Inline edit the "Status" field:
Card views	Change the layout of the task card and add different fields to provide the right level of information for your team.
Capacity planning	Define the capacity of teams and team members.
Quick filters	Filter data using previously created JQL filters in program configuration.
Show full scope	Load tasks from lower-level Boxes/hide tasks in lower level Boxes: When the filter button is pressed (dark grey background, white icon), only tasks planned on the level you currently see are visible. Tasks planned for lower-level Boxes are hidden. All tasks are shown when the filter button is not pressed (light grey background, dark icon). The button doesn't affect the backlog on the right because the backlog has its own separate show/hide lower-level tasks button.
Show tasks with dependencies	Hide tasks that don't have any dependencies: When the filter button (dark grey background, white icon) is pressed, only tasks with dependencies are visible. Tasks without dependencies are hidden. All tasks are shown when the filter button is not pressed (light grey background, dark icon). The button doesn't affect the backlog on the right - only task cards on the left are affected.
Search box	Quick search your tasks using: Task summary search JQL search
Timebox info	Additional information about the selected Timebox, which includes the Timebox ID.
Full-screen mode	Use this mode to hide Jira's and shared App headers.
Timeline	Dynamic timeline with "Today" and "Zoom" buttons. Click on the timeline's arrows to navigate between Iteration and Program Increments or to add a marker or an important event.
Infobar	The Infobar in the Board module provides information on crucial box content aspects, including: Backlog Dependencies Warnings
Back to backlog	Right-click on a task and select Back to backlog to move a task to the backlog.
Create a task-based objective	You can create a task-based objective directly in the Board module. Right-click on a task (Jira issue/basic task) and select Create objective based on this task. A new objective is immediately visible in the Objectives module.
Aggregate: Totals	Totals will help you plan and monitor the execution of your timeboxes (like PIs and Sprints). You can also use past data to analyze your teams' performance in depth.
Live sync	Jira admins can enable the Live sync feature. When enabled, any change to the tasks and the scope of the box will be updated.
Undo	Undo the last action. Important: Only a single action can be undone. The Undo button is grayed out by default. It becomes available when the user performs an operation that can be undone. Performing an undo operation OR reloading the page makes the Undo button grayed out again.
Task multiselect	You can streamline your work by selecting and moving multiple tasks.

Constraints

A task must be in the scope of a Box
Tasks based on external sources (Jira) have to be added to the scope of a box. The scope of a box can be changed in the scope definition section (Box configuration).

To be visible as a card on the Board

→ a task must be in one of the sub-box scopes.

It can be manually placed there (moved from Backlog onto the Board)

or automatic rules can be added in the scope definition.