Work on the board
Move cards between columns, respect work-in-progress limits and understand why a card goes back to its place.
On this page
The board shows the team's work in columns, one per status. In a Scrum desk it shows the active sprint; in a Kanban desk, the desk's continuous flow. Moving an item forward is as simple as taking its card to the next column.
Before you start
To move cards you must be a Lead, Member or QA of the desk. With the Viewer role you see the board, but you can't drag.
In Scrum, there must be an active sprint. If there isn't, the board shows There's no active sprint in this desk. and the Go to sprints button. See Start a sprint.
What it looks like
Go to Desks, choose the desk and press Board.
Below the title you see the context: in Scrum, the sprint's name, its goal, the days left and the points done against the total (for example, 12/30 pts); in Kanban, Continuous flow with work-in-progress limits.
Each column shows its name, the number of cards and the total of their points. If the column has a work-in-progress (WIP) limit, the counter includes it: 3/4 means 3 cards out of a limit of 4.
Each card shows the type, the number, the priority, the title, the epic, the points and the assignee's initials. Depending on the case, also:
Blocked, with a red left border. See Block an item.
Escalated, if the item comes from a service desk. See Escalate a ticket to development.
↺ with a number: the times QA rejected the item.
Subtasks done against the total, for example 2/5.
An amber left border if the item is at risk, for example because the sprint ends soon and the item hasn't reached QA yet.
When a column goes over its WIP limit, its header turns amber. Going over it is allowed, but it's a sign that the team is taking on more than it can finish.
Move a card
Drag the card to the target column. While you drag, the columns your role can't take it to are dimmed.
Drop it. The card changes column right away.
If the target column goes over its limit, you see the notice that it went over its work-in-progress limit.
Why a card goes back
If the move doesn't meet the desk's rules, the card goes back to its column and you see wasn't moved with the number and the reason:
Reason | What to do |
|---|---|
That transition isn't allowed for your role in this desk. | The lead restricted that step. Ask someone with the allowed role. See Transitions |
An approved QA verdict is missing (with every criterion "met"). | The item needs QA to approve it before moving to Done. See Acceptance criteria and QA |
The definition of done isn't complete. | Open the item's page and check the definition of done points. See Definition of done |
It has open subtasks: finish them first. | Finish the subtasks the notice lists |
Someone else just changed this item. It was reloaded: try again. | Move it again |
Move with the keyboard
Put the focus on a card (with Tab or a click).
Use ← and → to choose the target column. The chosen column is highlighted.
Press Enter to move it, or Escape to cancel.
With ↑ and ↓ you go from one card to another in the same column. Enter on a card you aren't moving opens its page.
Filter and organize
Search the board…: type and press Enter.
Everyone: choose a person to see only their cards.
Active sprint (Scrum only): choose another planned sprint to see its cards.
Swimlanes: No swimlanes, By person, By priority or By epic. It splits the board into rows. Your choice is remembered in your browser for that desk; the lead sets the default in Board and planning.
Board or List: the List view shows the same items in a table, with a Status selector on each row to move them without dragging.
What happens next
Clicking a card opens the item's page.
Other people's moves appear on your board by themselves.
When an item escalated from a service desk reaches Done, the service ticket gets a notification.