Boards, workflow, and sprints

Configure the team's flow and use Kanban or Scrum boards to track delivery.

Purpose

Boards show work within the flow configured by the team. The workflow defines the available statuses; the methodology determines whether work follows a continuous flow or iterations with a sprint. This guide explains how to configure and operate these three concepts together.

Prerequisites

Be authenticated with an active team.
Have board view permission to inspect the flow.
Have create permission to create boards.
To edit columns, archive, delete boards, or administer sprints, have edit, delete, or manage permission in the boards module.
To use sprints, configure the Sprint methodology in the team's workflow.

Key concepts

Board

A board belongs to a team and can be Kanban or Scrum. It has a name, description, emoji, accepted work item types, and columns. Each column groups one or more workflow statuses.

The board is an operational view: dragging an item to another column updates its corresponding status. The work item list remains the source for searching, editing metadata, and navigating the hierarchy.

Workflow

A workflow consists of a preset and ordered statuses. Each status has a name, key, category, color, and position. The observed categories are proposed, in progress, completed, and cancelled, but the displayed name may vary by preset.

Methodology

Kanban: continuous flow without time-boxing. The operation emphasizes cycle time and cumulative flow.
Sprint: work in iterations with dates, an objective, planning, velocity, and burndown.

The configured sprint duration, between 7 and 30 days, is a suggestion used when creating new sprints.

Configure the team's workflow

Open Team > Teams.
Select the team and open Workflow Settings.
Choose a workflow preset.
Choose Kanban or Sprint.
If the methodology is Sprint, enter the suggested duration.
Review the changes and select Save Configuration.
Return to the board and confirm that the columns and sprint button match the configuration.

The configuration belongs to the team, not to an individual. A change affects the next operations of all members in that context.

Switch from Sprint to Kanban

The application asks for confirmation because the change alters the experience. Existing sprints are kept, but there is no longer a current sprint and sprint-specific resources are hidden. Work items remain in the state they were in.

Create a board

Open Boards and select New Board.
Choose Custom or a quick-start template.
Select Kanban or Scrum when the team's methodology allows it.
Enter a name, description, and emoji.
Select the team if you have permission for more than one context.
Select the work item types the board should accept.
Confirm the creation.

Templates can fill in the initial name, description, emoji, types, and columns. Custom creates a board from the team's workflow.

Configure columns

Open the board.
Select Configure.
Create or edit columns, and change their name, color, or position.
Associate workflow statuses with each column.
Mark the completion column when applicable.
Save the configuration.

A column can represent more than one status. The board does not create a new status just because a column was created: configure the team's workflow first.

Work on the board

Open an active board.
Use the current sprint filter, a specific sprint, or all sprints when the team uses Sprint.
Filter by type, priority, assignee, or Only mine.
Drag a work item to the destination column.
Visually confirm the new status and wait for the update.
Use Quick add in a column to create an item in the board's context.
Open the item to edit its description, assignees, dates, tags, and other properties.

On mobile, the board uses column navigation, filter sheets, swipe actions, and batch selection. Board filters and sorting are persisted locally for the user.

Cascading movement

The organization can enable Cascade Status Move. When this option is on, moving an item automatically updates the status of its children, grandchildren, and great-grandchildren. Review the hierarchy before moving a parent item because the action can affect several work items.

Manage sprints

Sprint management is opened with the Sprints button inside Boards or a specific board; the current product does not have a separate sprint page.

Open Boards.
If the team uses Sprint, select Sprints.
Create a sprint with a name, dates, objective, notes, and planned points.
Open the sprint to view planning and associate work items.
Set a planned sprint to Current when it is ready.
Track completed points and progress.
When it ends, complete or cancel the sprint according to the actual outcome.

The observed sprint states are planning, active, completed, and cancelled. The panel separates the current sprint, planned sprints, and completed or cancelled sprints.

For agents

Before moving an item, read the columns and status mapping for the current board.
In a Sprint team, confirm the current sprint before adding items to or removing them from its scope.
In a Kanban team, do not try to assign a sprint just because an item has story points.
After moving a parent, check whether the organization has enabled cascading status movement.
When creating on a board, inherit the team, board, column, and sprint only when the request makes that context clear.
Report the change in terms of item, column, status, and sprint, not only as “moved.”

Current states and limitations

Current state: the application provides Kanban and Scrum boards, configurable columns, drag-and-drop, quick add, filters, favorites, archiving, cloning, and sprint management. The behavior of each flow depends on the methodology and the team's permissions.

The sprint button is enabled only when the team's methodology is Sprint.
/sprints redirects to Boards; management takes place in a side sheet.
Switching to Kanban keeps existing sprints but removes the current sprint and hides sprint-specific resources.
The creation board offers only Kanban and Scrum; other types declared in the model are not presented as options.
Archived boards are excluded from the default list; use the archived or all filter to find them.
Editing a board from another team requires management permission in addition to edit permission.
Favorites are a navigation preference; they do not change board visibility or permissions.
Analytics and sprint metrics depend on sufficient data and the selected methodology; do not conclude that a zero metric means there is no work without checking the filters and period.

Next steps

Create work items and associate them with the board.
Read Work items to understand hierarchy, statuses, and batch actions.
Use Settings and permissions to configure organization rules.
Record important workflow decisions in Memories.