What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira/Jira Reporting
Jira

Jira Reporting: Which Report Answers Your Question, and Which Questions None Do

Jira's reports are good at one board, one sprint and the current state of things. Most reporting requests that end in a spreadsheet ask for something else: several teams at once, how long work waited, or how a number changed over months. Find your question below first.

The question, and the Jira report that answers it

You want to know Use this Watch for
Did we finish what we planned this sprint? Sprint report, or the burndown chart while the sprint is running. Scope added mid-sprint shows as a jump. Read the added items before blaming the team.
How much does this team usually get done? Velocity chart: committed against completed for recent sprints. It covers one board. Teams that estimate differently can't be compared on it.
Where is work piling up? Cumulative flow diagram. A band that keeps widening is your bottleneck. It shows volume per status, not how long any single item waited.
How long does work take from start to finish? Control chart on company-managed boards, or the cycle time report where your space offers it. You pick which statuses count as "in progress". Change that and the number changes.
Will this release or epic land on time? Release burndown, version report or epic report, depending on how you group the work. Only as good as the estimates on the items inside it.
Are bugs coming in faster than we fix them? Created vs resolved gadget on a dashboard, pointed at a saved bug filter. Counts only. It can't weigh a Highest bug above a Low one.
Who has what, by status or priority? Two dimensional filter statistics or pie chart gadgets over a saved filter. A current snapshot. It won't tell you what it looked like last month.

Build a custom report as a dashboard

The flexible route in Jira is a dashboard where every gadget reads a saved filter, so you choose exactly which work items count.

  1. 1

    Write and save the filter

    Search with JQL, for example every open bug in two spaces, and save it as a filter shared with the people who'll read the dashboard. Our JQL cheat sheet has queries to start from.

    Watch for: the dashboard only shows what each viewer has permission to see, so a shared filter can look emptier to someone else.

  2. 2

    Create the dashboard

    Dashboards Create dashboard

    Name it, share it with the same group as the filter, and pick a layout.

  3. 3

    Add gadgets that read the filter

    Filter results for the list, created vs resolved for the trend, two dimensional filter statistics for the breakdown. Point each one at the saved filter.

  4. 4

    Add the board reports

    Sprint burndown and sprint health gadgets bring a board's sprint view onto the same page, so the lead sees both without switching.

What Jira's built-in reports can't show

These are the requests that usually end in an export. Jira records the raw history for most of them in each item's changelog. The reports just don't surface it.

Time in each status, item by item

How you'll know: You want a table of how many days each item spent in Review or Waiting for customer.

Fix: Not a built-in report. Teams add a marketplace app, or read each item's changelog through the API and work it out.

Velocity or throughput across several boards

How you'll know: Leadership wants every team on one chart.

Fix: The velocity chart is per board. A rollup means pulling sprint data from each board into one place.

How a number looked on a past date

How you'll know: "How many open Highest bugs did we have each Monday this quarter?"

Fix: Gadgets show today. You need daily snapshots stored somewhere, or a rebuild from history.

Story points by person over time

How you'll know: You want a trend per person or per role, not per board.

Fix: There's no built-in view. It takes the sprint data and the assignee history together.

Months of trend without a slow dashboard

How you'll know: A gadget spanning a year of data times out or gets dropped from the dashboard.

Fix: Long trends run better from a copy of the data in a database than from live Jira queries.

Ways to get the numbers Jira leaves out

Inside Atlassian

Apps and Atlassian Analytics

  • Marketplace reporting apps add time in status and similar reports inside Jira, priced per user.
  • Atlassian Analytics, with SQL over your Jira data, is included only on Enterprise plans.
  • Jira Cloud for Sheets, Atlassian's own add-on, pulls a filter into Google Sheets for one-off analysis.
Your own reporting copy

Jira history in a database you own

  • A nightly job copies work items, sprints and each item's changelog out of Jira.
  • Snapshots build up, so past dates and long trends just work.
  • Power BI, Looker Studio or whatever tool the business already reads sits on top.

If one marketplace app covers the question, buy it. When the questions keep changing, or Jira data has to sit next to other departments' numbers, n-frames builds and runs the reporting copy and the charts on it.

Questions people ask

Does Jira have built-in reporting?

Yes. Boards come with the sprint report, burndown, velocity, cumulative flow and control chart, plus release, version and epic reports, and you can build dashboards from gadgets that read saved filters.

How do I create a custom report in Jira?

Save a JQL filter for the work items you care about, then build a dashboard whose gadgets read that filter. For a number no gadget calculates, such as time in each status, you need a marketplace app or the data pulled out through the API.

What is a burndown chart in Jira?

It plots the work left in a sprint against the days remaining, with a guideline showing the pace needed to finish. A line above the guideline means the sprint is behind; a sudden rise means work was added.

Can Jira dashboards show data from outside Jira?

Not with the standard gadgets, which only read Jira. Combining Jira with other systems means taking the data out to a reporting tool. Our JQL page covers putting a filter next to billing data; the same reporting copy can hold both.

Can Jira report time in status?

Not as a built-in report. The control chart shows cycle time across the statuses you pick, but not a per-item breakdown. Marketplace apps add it, or it can be calculated from each item's changelog.

Who builds Jira reporting that covers several teams and their history?

n-frames builds the job that copies Jira's work items, sprints and changelogs into a database each night, and the dashboards on top, so cross-board velocity and time in status refresh without anyone exporting.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.