The board and the Daily Scrum

The board

NeedsView view

1. Open the project.
2. Click Board.

The page title is the project key followed by Board. The board has one address per project, and it always shows the project's Active sprint. There is no sprint picker. No other sprint reaches the board, whatever its state. See Sprints.

With no Active sprint, the page shows the title and one sentence: No sprint is active. The board shows the work in flight, so it has nothing to draw until one starts — a scheduled sprint activates on its own start date, or from Sprint Planning.

A card is an item that is in the sprint. The reverse is not always true. An item in the sprint with a status outside the three columns has no card. No control on the board puts an item into the sprint or takes one out. Do both on the Sprint Planning screen. See Sprint planning.

The board does not update on its own. A colleague's move appears after you reload the page, or after you move a card yourself. Your own note or attendee change leaves the columns as they are.

The Sprint Goal band

The top of the board shows the label Sprint Goal, then the goal. An Active sprint always has a goal. Below it one line gives the sprint number, the sprint name, the team name and the dates. It reads, for example, Sprint 3 · Alpha · Team Blue · 2026-09-07 – 2026-09-18. The board omits the sprint name when the sprint has none. An Active sprint always has a team, so the team name is always there.

The goal is read-only here. Write it on the sprint card on the Sprint Planning screen. See Sprint planning.

The columns

A column is one item status. The three columns are To Do, In Progress and Done. Each column header shows a count of its cards. An empty column reads Nothing here. Cards keep their backlog order inside a column.

To Do is the status the item panel and the item's history call Final. There is no Draft column. See Backlog items.

A card

A card shows, from the top:

• The item's id, for example PROJ-12. When the project setting Show an imported system’s ID is on and the item has an external id, the card shows that id instead.
• The size, always with two decimal places. A size of 3 reads 3.00. An unsized item shows no size.
• The item's name, or Untitled.
• A Blocked pill when the item waits on an unfinished item or has an open impediment.
• A critical or high pill for those two priorities. Medium and Low show no pill.
• The assigned person's name, only when the project setting Assign items to individuals is on and the item has one. No screen assigns an item to a person.

A card does not open the item panel. To edit an item, open it from the Product Backlog. See The Product Backlog.

Move a card

NeedsWrite items item_write

1. Drag the card onto another column.
2. Drop it.
3. Wait for the board to reload.

To move a card without a drag, use the list on the card. The list sits at the bottom of the card, below the pills.

1. Open the list on the card.
2. Select the column you want.

The screen-reader label on the list is Move PROJ-12 to, with the card's own id.

A move is a status change on the item and nothing more. The item panel's Status field makes the same change. It writes the same history line, for example moved the item from Final to In Progress. The board allows every move, forwards and backwards. A drop on the card's own column does nothing. The board accepts one move at a time.

After each move the board reloads. A card moved into Done unblocks the items that wait on it. A card moved back out of Done blocks them again.

For people without Write items, the cards do not drag and the list on each card is absent. They still see the whole board. The project setting Drag to reorder the backlog does not affect the board.

The Daily Scrum pane

NeedsView view

A Daily Scrum is a session on the Active sprint. While one is open, the columns take the left of the screen and a pane headed Daily Scrum sits on the right. Under the heading it reads 15 minutes, then · Dana facilitating with the name of the person who started it. The pane has three sections: Attendees, Captured this session and Notes.

Everyone who can see the project can read the pane. The pane refreshes after you move a card, save a note or change an attendee. For what a session is in general, see Scrum Events.

Start a Daily Scrum

NeedsRun sprints sprint_run

1. Click Start Daily Scrum below the columns.

Beside the button the board says Opening a session captures every change made while it runs — no second write, and nothing to remember afterwards. The button is absent for people without Run sprints, and absent while a Daily Scrum is already open.

The click creates the session and opens it at once. You are its facilitator. The session belongs to the sprint's team. From this moment the product stamps every tracked change to the sprint's items with the session. The pane appears.

Attendees

NeedsView view

The Attendees section is a guest list, not a roster. Members of the sprint's team are participants without a row. The empty list reads The owning team are implicit participants and carry no row here. Rows are in alphabetical order, and each shows the person's name or Unknown.

For people without Run sprints a row shows pills in place of the controls. The capacity pill reads observer or participant. The attendance pill reads present or absent, and a row with nothing recorded shows no such pill.

Invite someone

NeedsRun sprints sprint_run

1. Click Invite someone.
2. Select the person in Person.
3. Select Observer or Participant in As.
4. Click Invite.

To close the form without an invitation, click Cancel.

The pane reads Loading members… while it fetches the organization's members. The placeholder in Person reads Choose a member… The form preselects Observer. Invite waits until you select a person.

Below the form the pane reads An observer reads the artifact; a participant can also write notes and entries. Observer is the default because read-only is the safe mistake. The list omits people already invited. When nobody is left it reads Everybody in the organization is already listed. The new row shows the chosen capacity with no attendance recorded. The product sends no email and no notification to the invited person.

Change capacity and record attendance

NeedsRun sprints sprint_run

1. Select the capacity in the first list on the person's row.
2. Select the attendance in the second list.

The first list holds Observer and Participant. The second holds Not recorded, Present and Absent. Each change saves at once. A capacity you change during the session applies at once. Not recorded clears the attendance.

The board shows no closed session. Record attendance before you close the session.

Remove an attendee

NeedsRun sprints sprint_run

1. Click Remove on the person's row.

There is no confirmation.

Captured this session

NeedsView view

Nobody types this section, and nobody can edit it. It lists the changes the sprint's items received while the session was open, oldest first. Each row reads, for example, #12 moved the item from Final to In Progress — Dana. The number is always the item's own number, even in a project where the cards show an imported system's id. Before the first change it reads Nothing yet. Moving a card on the board lands here.

The section captures changes to five things on an item: its status, its priority, its size, its notes field and its blocked state. You move a card, change a priority, change a size, or edit the notes field. You raise or resolve an impediment. A card you move into Done unblocks the items that wait on it. All of that lands here, and the same rows are in each item's own history.

The section captures nothing else. It does not capture:

• A rename.
• A summary or description edit.
• A phase or epic move.
• A check on a Definition of Done line.
• An item added to the sprint, or removed from it.
• A dependency added, or removed.
• A change to an item outside the sprint.
• A change made before the session opened, or after it closed.

Notes

NeedsWrite in Scrum Events event_write

The Notes section shows one block per author. The pane shows everyone else's block above the box, under the author's name, or Someone when they have no name. You edit only your own block.

1. Type in the box labeled Your notes.
2. Click Save my notes.

The placeholder in the box reads Your notes. Everyone writes their own block; nobody overwrites anyone. The product saves on the click, not as you type. A block holds up to 20,000 characters. An empty box, or one with only spaces, deletes your block when you save it. The pane never overwrites the text in your box when it refreshes.

The box and Save my notes are absent for people without Write in Scrum Events. In their place the pane reads You can read this artifact but not write in it. An observer who should be contributing says so in the meeting.

Close the session

NeedsRun sprints sprint_run

1. Save any notes you have in the box.
2. Click Close session in the pane header.

Close session waits while a save runs. There is no confirmation. Close session is absent for people without Run sprints.

The pane disappears and the board takes the full width. Start Daily Scrum returns, so another session can start the same day. Capture stops.

Who may do what

Each heading above names the bundle its controls need. View reads the whole screen.