Jira Dashboard with Velocity

Question

Hi Folks

I'm building a dashboard for my squads and I'd like to add a Velocity View

Does anyone know the JQL query used for the standard Jira Velocity report which shows Velocity Per sprint.

The best I've been able to do is

project = X AND sprint IN closedSprints() AND status IN ("Completed", "Done", "Deployed to production") AND issuetype IN ("Story", "Bug") AND resolved >= "2026-01-01"

Using Custom Chart I'm able to show per month - the current sprint is correct but the previous sprint points is incorrect :(

Vasyl Krokha _Broken Build_ · Answer

Hi @Jamie Scott ,

The core issue is that JQL-based approaches like closedSprints() with resolved dates don't accurately attribute story points per sprint - they can miscount items that moved between sprints or changed estimates mid-sprint, which explains why your previous sprint totals look wrong.

A proper velocity-per-sprint view needs to read directly from Scrum board sprint data (commitments, scope changes, completions) rather than relying on JQL filters and resolved dates.

Agile Velocity Charts solves this natively. You point it at your Scrum board(s), and it automatically tracks up to 10 velocity metrics — including commitment, completed work, added/removed scope, and estimation changes — broken down per sprint with accurate story point attribution. You can embed it directly on your Jira dashboard as a gadget for your squads. It also supports custom Done statuses if your workflow goes beyond the default board columns.

Documentation: Velocity chart overview · Custom Done statuses · JQL data sources
Interactive example: Sprint velocity chart — a clickable demo showing how the chart works
Marketplace: Agile Velocity Charts

The app is free forever for teams of up to 10 users. Let me know if you need help setting it up or have any other questions!

Alexey Pavlenko _App Developer_ · Answer

Hi @Jamie Scott ,

project = X AND sprint IN closedSprints() AND status IN ("Completed", "Done", "Deployed to production") AND issuetype IN ("Story", "Bug") AND resolved >= "2026-01-01"

I think in this query your are missing "AND resolved<=" for a starting point. You need time boundaries.

If you need more than this in the future consider the app I developed - Multi-team Scrum Metrics & Retrospectives.

It has support of various periods out-of-box - sprints, months, quarters, half-years, or years with the ability to display several number of periods and to drill down to the periods underneath. Also, you can display multiple teams in a single view. Plus, you can conduct in-place and quantifiable retrospectives.

A single bar analysis with drill-down from 2024 to H1 2024 - Screenshot #1 (years, issue count, 2 periods, 2 teams/boards):

Summary and trend of all sprints - Screenshot #2 (sprints, story points, 2 periods, 2 teams/boards):

Analysis and retrospective of one team bar - Screenshot #3 (sprints, story points, 2 periods, 3 teams/boards):

Best regards,
Alexey

Iryna Komarnitska_SaaSJet_ · Answer

Hi @Jamie Scott ,

Good question!

If you’re open to using a third-party app, I’d recommend trying the Sprint Report in Time in Status, an app my team built.

It lets you analyze completed sprints and includes a Team Velocity chart that compares committed vs. completed work for the last seven sprints, along with an average trend line.

To evaluate an active sprint, you can use the Burndown chart.

We also recently released a new feature that shows exactly what’s included in each metric—for example, which tasks were carried over, added, or removed during the sprint.

Hope this helps!