Skip to content
Tutorials Center
My learning

Topics

Lesson 16 of 29 ยท Boards, Sprints and Reporting

Boards, Backlogs and Sprints in Jira

Learn how Jira boards, the backlog and sprints work: Scrum vs Kanban boards, ranking, starting and completing a sprint, releases, with a runnable board model.

Issues are the raw material. Boards are where a team sees and moves them. A Jira board is not a separate store of data: it is a live view of issues, filtered by a query and drawn as columns that match workflow statuses. Move a card, and the issue's status changes; change the status elsewhere, and the card moves.

This lesson explains the two board types, the backlog, and the lifecycle of a sprint in Jira: plan, start, work, complete. The real Jira cannot run here, so screens and menus are described in words and the runnable examples are stand-ins: small JavaScript models of the rules (ranking, capacity, carry-over). They are not Jira's code, but the logic matches how teams use it.

Two kinds of board

Scrum board Works in time-boxed sprints.
Kanban board Continuous flow with WIP limits.

Same issues, same workflows, different rhythm.

1 / 2

Scrum boards and Kanban boards

Jira offers two board styles. They share columns and cards but differ in what surrounds them.

A Scrum board is built around the sprint. It shows only the issues in the active sprint, and it has a backlog screen where you plan the next sprints. It supports a sprint goal, story point estimates, the sprint report and the burndown chart. Use it when your team follows Scrum.

A Kanban board has no sprints. Work flows from left to right all the time, and you can set a WIP limit (work in progress limit) on a column; Jira highlights the column when the limit is exceeded. Kanban projects may still have a backlog, but it is just a list of what is not yet on the board. Use it for support queues, operations, or any team whose work arrives unpredictably. The ideas are explained in Kanban and WIP Limits.

Scrum board Kanban board
Time-boxed iterations Yes, sprints No
Backlog screen Yes, with sprint planning Optional
Estimates and burndown Story points, burndown, velocity Cycle time, control chart
Main limit Sprint capacity WIP limits per column
Typical team Product development Support, maintenance, ops

Columns and statuses

Each column is mapped to one or more workflow statuses. If your workflow has the statuses To Do, In Progress, In Review and Done, a four-column board with a one-to-one mapping is the natural layout. You can map two statuses to one column ("Blocked" and "In Progress" both under In Progress) when you want fewer columns than statuses, but not the other way round: a status can sit in only one column.

A board has a filter, a saved search written in JQL, that decides which issues appear. If an issue is missing from a board, the filter, not the board, is the first thing to check. Searching is covered in JQL and Filters.

The backlog and ranking

The backlog is the ordered list of work that is not in a sprint. Order is the priority: the issue at the top will be built first. Jira stores this as a rank. You drag issues up and down on the backlog screen, and the new rank is saved for everyone. This is the practical form of the Product Backlog from Scrum Artifacts and Commitments.

Two habits keep a backlog healthy:

  • Refine the top, ignore the bottom. The first one or two sprints' worth of issues should be small, estimated and have acceptance criteria. Items far down can stay as rough epics.
  • Delete or close what you will never do. A backlog with 900 items is not a plan; it is a graveyard that hides the real priorities.

The stand-in below keeps a backlog as an ordered array and moves items with an insertBefore helper, the same operation as a drag.

JS Ranking a backlog

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Creating, starting and completing a sprint

On a Scrum board's backlog screen, the flow looks like this:

  1. Create a sprint. Jira adds an empty sprint box above the backlog.
  2. Plan it. Drag ranked issues from the backlog into the sprint. Jira shows the total of story points as you go, so you can compare it with the team's velocity and capacity.
  3. Start the sprint. You give it a name, a start and end date (commonly one to four weeks) and a sprint goal. Only one sprint is active per board in the standard setup, and the issues now appear in the board's columns.
  4. Work. Cards move across columns. Scope can change, but the sprint goal should not; every added issue shows up in the sprint report as "added after the sprint started".
  5. Complete the sprint. Jira asks what to do with issues that are not in a Done-category status: move them to the backlog or to the next sprint. Done issues stay recorded in the finished sprint.

The stand-in below implements steps 2, 3 and 5: it fills a sprint up to a capacity, flags overload, and on completion returns unfinished work to the top of the backlog while computing the sprint's velocity (points finished).

JS A sprint board stand-in

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The warning is only a signal. Jira does not stop you from over-committing; the team decides, using its own history, which is why a stable velocity matters more than a single sprint's number.

Do not complete a sprint by dragging every unfinished card to "Done" to make the chart look good. The data is the team's feedback. Moving unfinished work to the backlog or next sprint is honest; hiding it teaches you nothing.

Releases and versions

A version (also called a release) is a named set of issues that ship together, such as 4.3.0. You assign issues to a version through the Fix versions field. The Releases page then shows how many of that version's issues are done, and marking the release as "released" records the date. A sprint and a release are independent: one release often spans several sprints, and one sprint can contribute to more than one release.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which board type has a sprint goal, story point estimates and a burndown chart?

    Scrum boards are organized around time-boxed sprints. Kanban boards focus on continuous flow and WIP limits.
  2. 2. In Jira, what decides which issue will be built first from the backlog?

    The backlog is an ordered list. Its order is the rank, and top items are built first.
  3. 3. A board is missing an issue you expect to see. What do you check first?

    A board shows what its saved filter returns, so the filter is the first suspect.
  4. 4. When you complete a sprint, what happens to issues not in a Done-category status?

    Jira asks where unfinished issues should go, usually the backlog or the next sprint.

Summary

  • A board is a live view of issues, defined by a filter and a column-to-status mapping.
  • Scrum boards use sprints, a backlog screen, estimates and burndown; Kanban boards use continuous flow and WIP limits.
  • The backlog is ordered by rank; the top of the list is what the team builds next.
  • Sprint lifecycle: create, plan, start with a goal, work, complete; unfinished issues return to the backlog or move on.
  • Versions (releases) group issues that ship together through the Fix versions field.
  • The JavaScript examples are stand-ins for these rules, not Jira's code.

Next, learn how to find any group of issues with JQL and Filters.