Sprint Velocity Chart for Jira — User Manual
1. What this gadget shows
For the last closed sprints of a board, the gadget shows:
- Committed — the work in the sprint when it started,
- Completed — the work that was done when the sprint closed,
- Added and removed — the work that moved in or out while it ran,
- Say-do — completed as a share of committed,
- Average velocity — the completed work of the last three sprints.
Below the chart, the sprint details show every change to one sprint: what moved, when, and who moved it.
It writes nothing to Jira, and it sends no data outside Atlassian.
2. Setting it up
- Open a dashboard and choose Add gadget.
- Add Sprint Velocity Chart for Jira.
- In the gadget, pick a board. The sprint details show the latest closed sprint; pick another sprint to see its details.
The gadget remembers your choice. Each gadget keeps its own, so two gadgets on the same dashboard can show two different boards.
3. Reading the gadget
3.1 Which sprints
The chart looks at the last six sprints that have started, and shows the ones that are closed. A sprint that is still running has no completed number yet, so it is not in the chart. The gadget says how many of the six were closed.
3.2 Committed and completed
We count these the way Jira's own velocity chart does:
- Done means a status in your board's last column.
- Points come from your board's estimate field — the one set in the board's settings.
- Each sprint is counted as it stood when it closed. An issue reopened later still counts as completed. An issue re-estimated later keeps the estimate it had at the close.
An issue that was removed before the sprint closed is not counted as completed, even if it was done.
3.3 Completed outside this sprint
An issue that was already done when it entered the sprint is shown as "completed outside this sprint (not counted)". Jira's velocity chart leaves it out too: it was not done in this sprint.
3.4 Points or issues
If your board estimates in story points, the gadget shows points. If the board counts issues, or if no issue in these sprints has a value in the board's estimate field, it shows issue counts and tells you why.
An issue with no estimate is not counted as zero. If completed issues had no estimate, the gadget says how many.
3.5 Say-do and average
Say-do is completed divided by committed, for one sprint. Work added during the sprint can push it above 100%.
Average velocity is the mean completed work of the last three closed sprints. If there are fewer than three, the gadget says how many it used.
3.6 The sprint details
Pick a sprint to see what happened while it ran: every issue added or removed, when, by whom, and its estimate at that moment. Changes made in one bulk action are grouped into one line.
4. What we can and cannot see
Issues you cannot see
The app asks Jira with your permissions. If an issue is hidden from you, it is not in your numbers — and we cannot flag this, because a hidden issue looks exactly the same to us as an issue that does not exist. Two people looking at the same gadget can see different numbers.
Your board's settings
To count the way Jira does, the app reads your board's columns and estimate field. If it cannot read them, it says so and falls back:
- Done then means a status in Jira's Done category. This is usually the same as your last column, but not always.
- The estimate field is then the one most used in your sprints.
Large boards
The gadget reads up to 2,500 issues per board, and it has a time limit. If a board is bigger, or Jira answers slowly, the gadget says so and marks the affected numbers with ~. A number marked ~ may be lower than the real one.
Sub-tasks
Sub-tasks are not counted — not in committed, not in completed. The sprint details say how many sub-tasks were left out.
Kanban boards
Kanban boards have no sprints, so there is no velocity to show.
5. Frequently confusing things
5.1 "Jira's velocity chart shows 0 points, the gadget shows –"
No issue had a value in the board's estimate field. Jira shows that as 0; we show it as "no estimate", because nothing was estimated. The issue counts still match.
5.2 "An issue is done, but it is not in completed"
Either it was already done when it entered the sprint (section 3.3), or it was removed from the sprint before the sprint closed (section 3.2).
5.3 "Say-do is above 100%"
More work was completed than was committed at the start. That usually means work was added during the sprint — the Added column shows how much.
5.4 "The numbers are different from my colleague's"
The gadget reads Jira with the viewer's permissions. See section 4, Issues you cannot see.
6. Permissions the app asks for
| Permission | Why |
|---|---|
read:board-scope:jira-software | To list your boards. |
read:board-scope.admin:jira-software | To read your board's columns and estimate field, so that done and points mean what they mean on your board. The app cannot change the board. |
read:sprint:jira-software | To read the board's sprints and the issues in them. |
read:issue-details:jira · read:jql:jira · read:project:jira | To read the issues of the board. |
read:epic:jira-software | Epics can be in sprints too; without this they would be missing. |
read:jira-work | To read each issue's change history (sprint, status, estimate). |
storage:app | To remember each gadget's board and sprint. Nothing leaves Atlassian. |
The app has no write permission. It cannot change anything in Jira.
7. Data and privacy
The app reads Jira through Atlassian's own API, with your permissions. It writes nothing back, and it makes no network calls outside Atlassian. It stores two numbers per gadget — the board ID and the sprint ID — on Atlassian's app storage. Remove the app and Atlassian soft-deletes them straight away, then erases them after its own retention period.
[ Full privacy statement → ]
8. Getting help
Email: support@axerilabs.com
We reply within two working days. Written support in English.
If Atlassian classifies an issue as critical, we reply within 24 hours, weekends included. A reply means we have read your report and told you what happens next. It does not mean the fix is ready: we do not promise a fix time.
We do not offer phone, video or live chat support.
If a number looks wrong, please read sections 4 and 5 first. If your case is not there, write to us: tell us the board, the sprint, and what you expected to see.