Skip to content
Tutorials Center
My learning

Topics

Lesson 18 of 29 ยท Boards, Sprints and Reporting

Jira Reports and Dashboards

Understand Jira's burndown, velocity, sprint report and control chart, plus dashboards and gadgets, and compute the same numbers yourself in runnable Python.

Jira records every change to every issue: when it was created, when its status changed, which sprint it belonged to, and what its estimate was. Reports turn that history into charts that answer questions like "Will we finish the sprint?" or "How long does a bug usually take?". Dashboards collect the charts and lists you care about on one page.

You do not need to memorize the screens. What matters is knowing what each report measures, what it cannot tell you, and how the numbers are produced. Jira itself cannot run on this site, so the report screens are described in words. The runnable examples are stand-ins: short Python programs, executed in your browser, that compute the same kind of numbers from sample issue data. They are not Jira's code, and Jira's exact rules (for example how it handles scope changes) are more detailed.

Which report answers what?

Burndown Are we on track this sprint?
Velocity How much do we finish per sprint?
Sprint report What was done, added or left over?
Control chart How long does work take?
1 / 2

The sprint burndown chart

A burndown chart shows how much work remains in the sprint, day by day. The horizontal axis is time. The vertical axis is the remaining estimate, usually in story points. Jira draws two lines:

  • The guideline: a straight line from the committed total down to zero at the end of the sprint. It is a reference, not a promise.
  • The remaining values line: the actual remaining points, which only drops when an issue moves to a Done-category status.

Three patterns are worth recognizing. A line that stays flat and then falls off a cliff on the last day means issues are being finished in one batch (or not being updated); a line that rises means scope was added; and a line well above the guideline in the middle of the sprint is an early warning to talk about the sprint goal. A burndown does not tell you if the right work was done, only how fast the estimate went down. The chart idea is also explained in Velocity, Burndown and Cumulative Flow.

The first stand-in computes the guideline and the actual remaining points from issue data, then draws a text chart.

Python Burndown numbers from issue data

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Velocity and the sprint report

The velocity chart shows, for each recent sprint, two bars: the points committed at the start and the points completed at the end. Plenty of teams average the last three to six completed values to forecast how much to plan next time. Two cautions: velocity belongs to one team, because point scales differ between teams, and it is a planning aid rather than a performance score. Chasing a higher number leads to inflated estimates (see Estimating with Story Points).

The sprint report lists a single sprint in detail: issues completed, issues not completed, issues removed, and issues added after the sprint began. It is the best view for a sprint review or retrospective because it shows where the plan changed, not just the totals.

The next stand-in builds a small velocity table with a rolling average and a simple forecast range for the next sprint.

Python Velocity and a forecast range

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The control chart and cycle time

The control chart plots each finished issue as a dot: the horizontal position is when it was resolved, the vertical position is how many days it took to go from a chosen start status to a chosen end status (its cycle time). Jira also draws a rolling average and a band around it. It is the most useful report for Kanban teams and the best tool for answering "how long will a typical item take?"

Averages hide too much, so also look at percentiles: "85% of issues were done within 6 days" is a far better promise than "the average is 3.5 days". A cluster of dots far above the line points to work that stalled, and those are the issues worth discussing in a retrospective. For the ideas behind cycle time and lead time, see Kanban and WIP Limits.

Python Cycle time, average and percentile

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice how one slow issue (12 days) pulls the average above the median. That is exactly why the percentile is the safer number to quote.

Dashboards and gadgets

A dashboard is a page made of gadgets. Each gadget is a small window onto your data: a pie chart of issues by assignee, a list of "assigned to me", a filter results table, a sprint burndown or a created-versus-resolved chart. Most gadgets are configured with a saved filter (see JQL and Filters), so the quality of a dashboard depends on the quality of the filters.

Good dashboard habits:

  • Build one dashboard per audience: a team dashboard for daily use, a short one for stakeholders.
  • Prefer a few meaningful gadgets over twenty colorful ones.
  • Name filters so a gadget's purpose is obvious ("SHOP: open bugs by priority").
  • Share the dashboard with the right people, and review it when the workflow or the team changes.

Reports are only as honest as the data. If people move all their cards to Done on the last afternoon, the burndown says nothing and the control chart reports near-zero cycle times. Update status when work really changes, and use the reports to start conversations, never to rank people.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. On a sprint burndown chart, what does a rising line in the middle of the sprint usually mean?

    The remaining total only goes up when work is added or re-estimated upward. The sprint report lists issues added after the start.
  2. 2. Why is a percentile such as the 85th more useful than an average for cycle time?

    A few long-running items distort an average. Saying that 85% of issues finish within N days is a more reliable statement.
  3. 3. Which report lists issues that were added after the sprint started?

    The sprint report separates completed, not completed, removed and added-after-start issues.
  4. 4. What is the best way to use velocity?

    Velocity is team-specific planning information. Turning it into a target encourages inflated estimates.

Summary

  • A burndown shows remaining work day by day against a guideline; a rise means added scope, a cliff means batch updates.
  • The velocity chart compares committed and completed points per sprint; use a short average for planning, never as a score.
  • The sprint report shows completed, unfinished, removed and added issues for one sprint.
  • The control chart shows cycle time per finished issue; quote percentiles instead of averages.
  • Dashboards combine gadgets, and gadgets are driven by saved filters.
  • The Python examples are stand-ins that show how such numbers are computed; Jira's exact calculations are more detailed.

Next, learn how teams customize Jira: Workflows, Permissions and Customization.