Velocity Chart for Jira — Documentation

The sprint velocity chart the native report doesn't give you — on any dashboard, any board type, with your own Definition of Done.

Contents

  1. Overview
  2. Quick start
  3. Configuration
  4. How velocity is calculated
  5. Multiple boards
  6. Export
  7. Free vs Pro
  8. FAQ & Troubleshooting
  9. Support

1. Overview

Velocity Chart adds a clean sprint velocity chart to any Jira dashboard. For each closed sprint it shows committed (grey) versus completed (green) work, a dashed average-velocity line, and your say/do ratio.

Velocity chart showing committed vs completed bars with an average line and say/do ratio

2. Quick start

Step 1 — Install from the Marketplace

  1. Go to Velocity Chart for Jira on the Atlassian Marketplace and click Get it now.
  2. Choose your Jira site and confirm. Free for up to 10 users.

Step 2 — Add the gadget & pick a board

  1. Open a Jira DashboardAdd gadget → search for Velocity ChartAdd.
  2. Click the gadget's pencil / Edit icon.
  3. Pick a Scrum board (company-managed or team-managed) → Save.
Adding the Velocity Chart gadget to a Jira dashboard
Note: velocity needs a Scrum board with at least one completed sprint. Kanban boards have no sprints and won't appear in the picker.

3. Configuration

Everything is configured from the gadget's Edit mode:

The gadget configuration form including the configurable Done-status mapping
SettingWhat it does
Board(s)The Scrum board to chart. Team-managed boards are tagged “team-managed”. PRO Select up to 4 boards to compare.
Sprints to showHow many recent closed sprints to display. Free: up to 7, Pro: up to 20.
Sprint labelsFull name or Numbers only. Long names are shortened on the axis; hover a label for the full name.
Estimation PROStory Points (the board's estimation field, with a fallback to the standard Story Points field), Issue count, or any numeric custom field.
Count as “Done” PROChoose exactly which statuses count as completed. Defaults to your board's Done column. This is the key difference from Jira's built-in report.
Include sub-tasks PROOff by default (matches Jira's native behaviour). Turn on to include sub-task estimates.
Tip: if the bars look empty, your team estimates in a different field than the board default. Set Estimation → Custom numeric field to the field you actually use (e.g. Story point estimate).

4. How velocity is calculated

For each closed sprint the gadget shows two bars:

Average velocity is the mean completed work across the displayed sprints (the dashed line). Say/Do ratio (predictability) is completed ÷ committed — how reliably the team delivers what it commits to.

About committed work: committed is reconstructed over the issues still in the sprint at close. An issue committed at the start but removed before close is not counted — this only under-reports committed when scope was actively removed mid-sprint (uncommon).

5. Multiple boards PRO

Select several Scrum boards in one gadget to compare them side by side. Each board gets its own compact chart with its own average and say/do, all using the same estimation and Definition of Done — so you compare like for like in a single dashboard slot.

Two boards compared in one gadget with a shared configuration

6. Export PRO

7. Free vs Pro

Velocity Chart has one simple plan — there is no separate “Free” edition to buy up front. The app is free for teams of up to 10 users, and larger teams get a free trial. Pro features unlock automatically while your site has an active subscription (the free trial counts too).

You land on the reduced Free experience when a site has no active subscription — typically a larger team after its trial ends, or after a paid subscription is cancelled. The gadget never switches off: it keeps drawing a single-board velocity chart (the board's default Done and estimation, up to 7 closed sprints) so you don't lose access to your data. Re-subscribe at any time and the Pro features come back instantly.

Feature comparison

CapabilityFreePro
Single-board velocity chart + average line
Company- & team-managed Scrum boards
Sprints shownup to 7up to 20
Configurable Definition of Done
Estimation mode (issue count / custom field)board default
Include sub-tasks
Predictability / say-do
Multiple boards in one gadget
CSV & SVG export

Which plan is right for you?

 FreePro
Best forSmall teams and a quick single-board velocity check.Several teams, custom workflows, and reporting or forecasting.
AdvantagesNo setup and no cost — a real committed-vs-completed chart with the average-velocity line, on any dashboard and any board type (including team-managed).Velocity measured your way: configurable Definition of Done, estimation modes, sub-task control, predictability (say/do), multi-board compare, more sprints, and CSV/SVG export.
LimitationsOne board · the board's default Done & estimation · up to 7 sprints · no predictability or export.Per-user subscription once a site has more than 10 users.

Free for teams of up to 10 users. See the Marketplace listing for current per-user pricing.

8. FAQ & Troubleshooting

It says “No closed sprints found”.

The board has no completed sprint yet. Start and complete a sprint, or pick a board that already has closed sprints. Kanban boards have no sprints.

The bars are empty / zero.

Your issues are estimated in a different field than the board's default. Open Edit → Estimation and choose the field your team actually uses (e.g. Story point estimate), or switch to Issue count.

A board is missing from the picker.

Only Scrum boards (company- and team-managed) appear; classic Kanban boards are excluded because they have no sprints. Newly created boards appear immediately — the picker is not cached.

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

The native report is hidden on the board, locked to one board, tied to a fixed Done column and estimation field, and weak on team-managed projects. This gadget lives on any dashboard, works on every board type, lets you define “Done” and the estimation field yourself, compares multiple boards, and adds predictability and export.

Do you support team-managed projects?

Yes — fully. Team-managed Scrum boards appear in the picker tagged “team-managed” and use the same calculation.

Does the app change my issues?

No. Velocity Chart is strictly read-only and requests no write permissions. See the Security Policy.

9. Support

Questions, bugs, or feature requests? We typically respond within 1–2 business days.
Email: support@janekbehrens.de
More: Support · Privacy · Security · Terms