How to Create a Scrum Board in Jira

Before building one, it helps to look at an established example. A space like "PMN Online's Scrum" shows the pattern: an active sprint at the top, dated and scoped, listing its work items with statuses like To Do, In Progress, and In Review, and a separate Backlog section below holding items not yet pulled into a sprint. That's the structure a Scrum board exists to support: a defined sprint window sitting above an unscheduled backlog.

From the left sidebar under Spaces, open the space you're setting the board up in, for example one called TEST SPACE. Its existing boards are listed underneath, such as a "TS board." A new board is typically created alongside a space's existing backlog and board list instead of from a blank slate.

From within the space's backlog view, use the add action (the + control near the board list) to open Create a board, then choose Create a Scrum board. There's a second route to the same dialog: the global search field (or the / shortcut), then "Go to all: Boards," then Create board.

Either way you land on a short form: a required Name this board field, and a required "Choose what to include in this board" dropdown. One limit worth knowing before you start: team-managed spaces don't support adding extra boards this way, since each ships with exactly one board already. If you don't see the + control, you're likely in a team-managed space, and a saved-filter-based board from the global route is the workaround.

Give the board a name your team will recognize at a glance, tied to the sprint cadence or the team itself, not something generic. Basing the board on a space auto-generates a filter behind the scenes, roughly space = "YOUR SPACE" ORDER BY Rank ASC, so getting the include dropdown wrong is the most common reason a freshly created board looks empty: the filter ends up pointed at the wrong space, or none at all. Double-check the selection before clicking Create, since a board's type (Scrum or Kanban) can't be changed after it's made.

Click Create. The new board appears in the space's board list in the sidebar alongside any others.

Open it once to confirm it shows the work items you expected. If it's empty, check the board's underlying filter and its JQL before assuming something broke. That filter, not the board itself, decides what shows up.

A Scrum board is only useful once its backlog has real work in it. Add the issues your team plans to tackle, prioritize by dragging them into order, and give each enough detail, a clear title plus any relevant labels or story points, that whoever picks it up doesn't need to ask what it means.

Then select the items for your first sprint and start it, the same way the sprint at the top of the PMN Online's Scrum example is dated and scoped. Once started, those items move onto the active board where the team drags them across statuses as work progresses.