Issue on Velocity chart report - committed is BLANK

Question

Good day!

I would like to seek your help as to why our last 2 sprints in the Velocity Chart report are missing inputs on Committed SP.

I am not aware of any changes in our board.

When I checked the backlog insight from the backlog view, it is displaying the committed SP for current (Which I assume it is the same for the previous sprints that we have).

We are using JIRA Cloud version.

Iryna Komarnitska_SaaSJet_ · Answer

Hi @Sherwin Soriano ,

When Committed is blank/zero on the Velocity chart, it usually means Jira didn’t capture any estimates at the moment the sprint was started. This often happens when:

Issues were added to the sprint after you clicked Start sprint, or

Story points/estimates were added or changed after the sprint started.

I’d suggest checking the Sprint Report and issue history for those two sprints to see when the sprint field and estimates were set — that usually explains why Jira shows 0 committed even though the backlog insights look fine.

Small disclosure: I’m part of the Time in Status team.If you need deeper sprint analytics, the Sprint Report in the Time in Status for Jira app shows:

committed vs completed for the last 7 sprints,

team workload per assignee,

completion rate and carryover,

scope change (added/removed work),all based on your board’s estimation method (story points, original estimate, or issue count).It can give a much clearer picture of why numbers look off in native Velocity and how your team actually performed in each sprint.

Alexey Pavlenko _App Developer_ · Answer

Hi @Sherwin Soriano ,

Most likely, you added scope to the sprint after it had already started. If that’s the case, you need to make sure the sprint is fully planned before it starts. Unfortunately, the Sprint Report doesn’t include a Final Scope metric. If you want to see the complete list of tasks in a sprint under a single metric, you can install the app I developed - Multi-team Scrum Metrics & Retrospective.

With it, you will get the view below:

Best regards,
Alexey

Danut M _StonikByte_ · Answer

Hi @Sherwin Soriano,

Possible reasons for this:

* the issues were added in sprint after the sprint was started 
* you added SPs on the issues after the sprint was started
* the sprint was actually started after the Sprint Planned Date/wiki

Look also at the Sprint Burndown Report for that sprint to see what happened and how the Remaining was when the sprint started. Last column indicates the Initial Commitment.

Also, compare this sprint start date with the start date from the Sprint report. They should be the same.

Another alternative would be to try an app (plugin) from the Atlassian Marketplace that provides a similar velocity chart. Our Great Gadgets app includes a Team Velocity gadget that may not experience this issue, as it works slightly differently from Jira’s built-in reports. In addition, it offers extra metrics such as Final Scope, which can be helpful in cases where the Initial Scope is zero.

Danut