Velocity Chart for JiraJira Cloud · Built on Forge

Sprint velocity on any dashboard

Committed vs completed for your last closed sprints, with the average line and the say/do ratio. You decide which statuses count as done.

Try it free on Marketplace → Read the docs

Free for Jira sites with up to 10 users. Larger sites start with a free trial.

Sample data in your browser. Nothing is saved and nothing is sent anywhere. Dashed frames mark the parts that come from the app. Pro features are on, as in the free trial. Real screenshots below ↓

In your Jira

What you get

Screenshots from a real Jira site with sample data.

Velocity Chart gadget on a Jira dashboard: ten closed sprints with committed and completed bars, a dashed average line, average velocity 26.3 points and 81% say/do

Velocity on any dashboard

Committed (grey) and completed (green) for the last closed sprints of a Scrum board, with a dashed line for the average.

Avg velocity next to the board name, plus say/do in Pro.
Hover a bar for its value, click it for the issues behind it (Pro).
Company- and team-managed Scrum boards.

How velocity is calculated →

Video

Watch the tour

A short walkthrough of Velocity Chart in Jira.

Why the app

Jira alone vs. with Velocity Chart

	Jira alone	With Velocity Chart
Where you see velocity	The velocity report on the board's Reports page	A gadget on any Jira dashboard, next to your other gadgets
What counts as done	The board's Done column	The statuses you tick, for example Done and Ready for release (Pro)
How work is measured	The board's estimation setting	Story Points, issue count or a custom numeric field, set per gadget (Pro)
Several teams	One report per board	Up to four boards in one gadget, with the same settings (Pro)
Which issues make up a sprint	The sprint report on the board's Reports page	Click the sprint on the dashboard: committed or added later, done at the close or carried over (Pro)

Compared with Jira Cloud without apps. With the board's own Done column the app counts like Jira's report; differences come from your own settings or from issues removed during a sprint: how velocity is calculated.

Plans

Free and Pro

Free for Jira sites with up to 10 users. Larger sites start with a free trial; per-user pricing is on the Marketplace listing.

Free

When the site has no active subscription, for example after the trial.

One board per gadget
Velocity chart with the average line
The last 1 to 7 closed sprints
The board's estimation and its Done column
Company- and team-managed Scrum boards

Pro

While the site has an active subscription, the free trial included.

Up to 4 boards in one gadget
The last 1 to 20 closed sprints
Count as “Done”: the statuses you choose
Story Points, issue count or a custom numeric field
Include sub-tasks
Say/do ratio
Sprint details: the issues behind each bar
CSV and SVG export

Setup

Running in three steps

Install

Get the app from the Atlassian Marketplace and confirm the installation on your Jira site.

Add the gadget

Open a Jira dashboard, click Add gadget and search for Velocity Chart.

Pick a board

Click the pencil, tick a Scrum board with at least one closed sprint and click Save.

FAQ

Common questions

More answers in the documentation, or write to support@janekbehrens.de.

How is this different from Jira's built-in velocity report?

Jira's report lives on the board's Reports page and uses that board's Done column and estimation setting. Velocity Chart is a dashboard gadget: you choose which statuses count as done and how to estimate, chart up to four boards in one gadget, click a sprint to see the issues behind its bars, and get an average say/do ratio and CSV/SVG export (Pro).

Does an issue that was carried over count in both sprints?

Only as committed. Completed adds up the issues that were done when the sprint closed, as in Jira's own velocity report. An issue that was carried over unfinished counts as completed only in the sprint in which it was finished. Committed is the work that was in the sprint when it started and not yet done.

Does it work with team-managed projects?

Yes. Team-managed Scrum boards appear in the board picker tagged “team-managed” and use the same calculation as company-managed boards.

Which Jira do I need?

Jira Cloud and a Scrum board with at least one closed sprint. Velocity Chart is a Forge app and runs on Atlassian's infrastructure; there is no Data Center or Server version. Classic Kanban boards have no sprints and are not listed.

Does the app change my Jira issues?

No. Velocity Chart only reads sprint data and requests no write permissions. It keeps a short-lived cache of the sprint data (issue IDs, keys, estimates and statuses; no titles, no people) in Atlassian's Forge storage. No external servers operated by Janek Behrens are involved. Details in the Trust Center.

Does everyone see the same numbers?

Everyone sees only the issues they can open in Jira, as in Jira's own velocity chart. When a sprint holds issues of a project or with a security level that someone cannot open, those issues are not counted or listed for that person, so numbers on a shared dashboard can differ between people. A short line under the chart says how many issues are hidden from you, never which ones. Who sees which numbers.

Is it free?

Jira sites with up to 10 users use it for free; larger sites start with a free trial. Without an active subscription, for example after the trial, the gadget keeps working in Free mode: one board, up to 7 sprints, the board's estimation and its Done column.

Also from Janek Behrens

Put your team's velocity on the dashboard