Jira Metrics and Team Reports: What to Track and How to Get It

Most Jira teams know what they should be tracking. The problem is getting that data out of Jira in a usable form. Velocity is scattered across board reports. Time logged is buried in issue worklogs. Team workload exists as individual issue counts but never aggregates clearly. And the moment you have more than one project, native Jira stops giving you a single view of anything.

This guide covers the metrics that actually matter for Scrum teams and project managers, where to find each one in Jira, and what requires an add-on.

Related: Types of Reports in Jira: for Agile, Scrum, and Project Management — the complete overview of every native Jira report type.

The Jira Metrics That Actually Matter

There are dozens of things you could track in Jira. Most teams track too many things badly rather than a few things consistently well. Here are the metrics worth tracking — grouped by who needs them.

For Scrum teams

For project managers

For team leads and Scrum Masters

Jira Software Reports: What’s Available Natively

Jira Software provides reports in two places — the Reports tab on Scrum and Kanban boards, and Dashboard gadgets. Understanding which is which prevents confusion when you can’t find something.

Board reports (Scrum)

Available under Project → Reports on any Scrum board. Four reports:

• Sprint Report — completed vs. incomplete issues, scope changes. Best for retrospectives.
• Velocity Chart — story points completed per sprint. Best for sprint planning.
• Burndown Chart — remaining work vs. ideal pace. Best for daily standups.
• Cumulative Flow Diagram — issue count by workflow status over time. Best for bottleneck identification.

All four are scoped to a single board. None can aggregate data across multiple projects or teams.

Full guide: Jira Scrum Reports: What Each One Shows and When to Use It

Dashboard gadgets

Available via Dashboards → Add gadget. Key ones for metrics tracking:

• Pie Chart — distribution of issues by type, status, priority, or assignee
• Issue Statistics — breakdown of issues by any field
• Average Age Chart — how long unresolved issues have been open
• Created vs. Resolved — backlog growth or reduction trend
• Workload Pie Chart — issue count distribution by assignee

Dashboard gadgets are more flexible than board reports because they work across any project via JQL filters. But they’re still limited — each gadget is configured independently, shows static data, and cannot aggregate across project hierarchies.

Full guide: Jira Charts and Graphs: Every Chart Type Explained

What Native Jira Can’t Give You

The gaps in native Jira metrics become clear as soon as teams grow beyond a single Scrum board:

• No estimation accuracy report. Jira stores original estimates and time spent, but provides no native view comparing the two across multiple sprints or issue types. This is one of the most commonly requested metrics and one of the biggest native gaps.
• No cross-project team report. Every native report is scoped to one board or project. A team lead managing two Scrum boards cannot see combined velocity or workload without exporting and combining data manually.
• No workload per sprint by assignee. The Workload Pie Chart shows issue count, not story points. It also resets every time you change the filter — it doesn’t show trends over time.
• No time tracking summary by user. Jira stores worklogs but provides no grouped summary of who logged what. The JQL workaround (worklogAuthor = "user" AND worklogDate >= -30d) returns a list of issues, not a total. See: Jira Time Tracking Reports.
• No scope change trend. The Sprint Report shows scope changes per sprint, but there’s no chart showing whether scope discipline is improving or worsening over time.

Jira Team Reports With Report Hub

Report Hub is a Forge-based Jira app that fills the most common native gaps without requiring data exports or external tools. It runs entirely inside Jira Cloud — your data never leaves the Atlassian environment.

The reports most relevant to team metrics:

• Workload per Sprint — story points and issue count by assignee per sprint, with trend over time. Shows whether work is balanced across the team and whether distribution is improving sprint over sprint.
• Estimation Accuracy — original estimate vs. actual completion across sprints and issue types. Answers whether the team is getting better at planning.
• Scope Change Report — issues added to sprints mid-cycle, visualised as a trend. Shows whether sprint planning discipline is improving.
• Cross-project Velocity — velocity chart aggregated across multiple Scrum boards. For teams managing more than one board, this replaces multiple separate velocity charts.
• Timesheet by User — total hours logged per person, by project and sprint, without exporting to spreadsheets.

All reports are connected by the Hub Filter — one filter that updates every report simultaneously when you change the project, sprint, or date range. Unlike native dashboard gadgets where each chart needs to be reconfigured individually.

How to Track Team Performance in Jira: A Practical Framework

Here’s the minimum viable metrics setup for a Scrum team — what to track, at what cadence, and where to find it:

Jira Enterprise Reporting: When You Need More Than Native

For organisations running multiple teams, multiple projects, or needing portfolio-level visibility, native Jira metrics become inadequate before long. The specific triggers:

• You have more than one Scrum board and need a combined velocity view
• Finance or operations needs time tracking data grouped by project or client
• Leadership needs a delivery status view across all active projects simultaneously
• You’re tracking estimation accuracy trends over quarters, not just single sprints
• You need to compare workload distribution across teams, not just within one

At that scale, the choice is between building a custom reporting integration (expensive, requires maintenance) or using a Marketplace add-on. For Jira Cloud teams, Report Hub is built specifically for this — cross-project, Forge-based, no external data pipeline required.

For teams that need fully custom analytics with MDX calculations and external data source integration, eazyBI is the more powerful option — though it requires a technical administrator to set up and maintain. See the full comparison: Best Jira Reporting Tools in 2026.

FAQ: Jira Metrics and Team Reports

What Jira metrics reports are available natively?

Jira provides native metrics through its Reports tab — Burndown Chart, Velocity Chart, Sprint Report, and Cumulative Flow Diagram for Scrum boards — and dashboard gadgets including Pie Chart, Issue Statistics, Average Age Chart, and Created vs Resolved. These cover sprint-level metrics for individual teams. Cross-project metrics, estimation accuracy, and time-based analytics require a reporting add-on.

What are the most important Jira metrics for a Scrum team?

The five most important Jira metrics for a Scrum team are: velocity (story points completed per sprint), sprint goal achievement rate (did the team complete what it committed to), scope change rate (issues added mid-sprint), estimation accuracy (original estimates vs. actual completion), and cycle time (how long issues take from start to done). Together these give a complete picture of team delivery health.

How do I track team performance in Jira?

Use the Velocity Chart (Reports tab) for sprint capacity trends, the Sprint Report to review completed vs. planned work each sprint, and the Burndown Chart to monitor sprint progress daily. For cross-team performance comparison, per-user workload, and time tracking analytics, use a reporting add-on such as Report Hub.

What is a Jira team report?

A Jira team report shows aggregated data about a team’s delivery — velocity, workload distribution, sprint completion rates, time logged, or estimation accuracy. Jira has limited native team reports (Velocity Chart and Sprint Report cover the basics). For cross-project team reports and per-user breakdowns, a reporting add-on is required.

What is a Jira project report?

A Jira project report shows the status, progress, and performance of a specific project — including issue completion rates, time spent vs. estimated, scope changes, and outstanding work. Jira’s native project-level reports are limited to the Version Report and Time Tracking Report. For comprehensive project reporting including cross-team views and progress dashboards, teams use reporting add-ons such as Report Hub.

What reporting and analytics tool works best with Jira?

For teams that need reporting and analytics inside Jira Cloud without building a data pipeline, Report Hub is the most practical option — it runs on Atlassian Forge, requires no setup, and provides prebuilt reports for agile metrics, time tracking, workload, and cross-project views. For fully custom analytics with MDX calculations, eazyBI is more powerful but requires technical administration.

Summary

Jira gives you the metrics to run a single Scrum team well — velocity, burndown, sprint goal achievement, basic workload distribution. The moment you need estimation accuracy trends, cross-project views, or time-based team analytics, you’ve reached the edge of what native Jira provides.

The practical answer for most teams: use native Jira reports for sprint-level operational metrics, and add Report Hub for the cross-project and performance metrics that native Jira doesn’t cover.

For the full list of every report type available in Jira, see: Types of Reports in Jira: for Agile, Scrum, and Project Management.

For agile-specific reports and how Scrum teams use them, see: Jira Scrum Reports: What Each One Shows and When to Use It.

Try Report Hub free on the Atlassian Marketplace →