Yes, team-managed projects have a velocity report
First, the good news. Team-managed Scrum projects do include a velocity report. Atlassian's team-managed velocity report documentation describes it clearly: velocity is the average amount of work the team completes per sprint, and in team-managed spaces it can be measured in story points or number of work items. As in company-managed projects, the grey commitment bar shows the total estimate of work in the sprint at start, and the green completed bar shows the total completed estimate at sprint end.
It sits alongside the other team-managed reports — the burnup chart, cumulative flow diagram, cycle time and deployment frequency — under the project's Reports section. So if you've been avoiding team-managed projects purely because of velocity, that reason no longer holds.
How to enable and find it
Velocity depends on sprints, so the prerequisite is the Sprints feature:
- Go to Project settings → Features and turn on Sprints (this also requires the board to be a Scrum-style board).
- Plan, start, and eventually complete at least one sprint — velocity only appears for closed sprints.
- Open Reports in the project sidebar and choose the Velocity report.
If reports look turned off, an administrator can re-enable them via the project's feature settings — Atlassian documents this in Enable reports.
How team-managed velocity differs from company-managed
The calculation is the same committed-vs-completed model. The differences are about configuration and reach:
| Team-managed | Company-managed | |
|---|---|---|
| Velocity report | Yes (story points or work-item count) | Yes (board's estimation statistic) |
| Configuration | Owned inside the project — quick to set up, less granular | Board-level estimation & column mapping |
| “Done” definition | The board's Done column | The board's Done column |
| Scope | That one project's board | That one board (boards can span projects via filter) |
| Dashboard gadget | None natively | None natively |
The headline: whichever project type you use, the velocity report is locked to one board, tied to that board's Done column, and confined to the project's reports area. Neither type gives you a velocity dashboard gadget, and neither lets you redefine which statuses count as done.
Why the velocity report is empty or wrong
The handful of things that trip up team-managed teams specifically:
- Sprints aren't enabled. No Sprints feature → no velocity. This is the number-one cause of a missing report.
- No completed sprint yet. Velocity is built from closed sprints; an in-progress sprint won't show.
- Estimation mismatch. If the project is set to measure in story points but issues are estimated in a different field — or not estimated at all — the bars come out empty. Switch the report to work-item count to sanity-check, or make sure points live in the field the report reads.
- Statuses outside the Done column. Work that's really finished but sits in a status not mapped to Done won't be counted as completed.
Worth knowing: team-managed workflows are owned per project, which makes it easy to add statuses like In Review or Released. That flexibility is great — but it's exactly the situation where the native velocity report, which only counts the single Done column, starts under-reporting your completed work.
Getting velocity onto a dashboard
The limitation team-managed teams hit most is reach. Velocity is stuck in one project's reports, while the team's shared, cross-project view is the dashboard. There's no native velocity gadget for either project type, so a Marketplace app is the only way to put velocity beside your sprint-health and burndown gadgets.
Velocity Chart for Jira is built for exactly this. It's a Forge-native dashboard gadget that treats team-managed and company-managed Scrum boards identically — team-managed boards even show a “team-managed” tag in the picker so you always know what you're charting. On top of that it adds what the native report can't: a configurable Definition of Done (count Released and Accepted, not just the last column), a choice of estimation field, optional sub-task inclusion, the say/do predictability number, and multi-board compare. Being Forge-native, it's read-only and your data stays on Atlassian.
For mixed estates: if your organisation runs a blend of team-managed and company-managed projects, a single dashboard gadget that handles both — with one shared Definition of Done — lets you compare their velocity on an equal footing, which the native per-project reports can't do.
Frequently asked questions
Do team-managed Jira projects have a velocity report?
Yes. Team-managed Scrum projects include a velocity report measured in story points or number of work items. It needs the Sprints feature enabled and at least one completed sprint, and sits alongside the burnup, cumulative flow, cycle time and deployment frequency reports.
Why is the velocity report missing in my team-managed project?
Usually because the Sprints feature is off. Enable Sprints in Project settings → Features, run and complete at least one sprint, and the velocity report appears under Reports. A team-managed project without sprints has no velocity.
Is team-managed velocity calculated differently from company-managed?
No — both use the same committed-vs-completed model. The differences are in configuration and reach: each is locked to one board, tied to that board's Done column, and confined to the project's reports area.
Can I show team-managed velocity on a dashboard?
Not with native Jira — there's no velocity dashboard gadget for either project type. A Forge app like Velocity Chart for Jira adds a dashboard gadget that works on team-managed boards and lets you configure the Definition of Done and estimation field.
Velocity on team-managed boards, on a dashboard
Velocity Chart for Jira treats team-managed and company-managed Scrum boards the same — with your own Definition of Done, estimation field and a dashboard gadget the native report doesn't offer.
Get it on Marketplace →