nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story Points mis-match between JIRA and EazyBI

Ryan_tcvdgh

A particular sprint's Velocity Chart Report shows 41 story points committed and 29 story points completed. When I create a report in EazyBI, EazyBI shows 31 story points committed and 26 story points resolved. Can anyone offer some guidance on how I can track down the discrepancy?

Accepted answers

eazyBI Support

Hi Ryan again,

Measure "Story Points resolved" is not directly related to "Sprint Story points commited" measure. "Story Points resolved" shows the total number of story points of the resolved issues, in the report context. It means, if you have selected a particular project in the report, then SP from the resolved issues of this project will be calculated.

Also, if you have selected Sprint in the report, then SP from the resolved issues which are added to the sprint, will be calculated. If some issue was added to the sprint previously, but now is added to another sprint, then story points from this issue would not be included in the result.

As, usually, resolved issues are not moved from the sprint, Story points resolved could be used to count resolved story points of the sprint.

To get the number of all planned Sprint Story points (not only on the first day of the sprint), you can combine measures Sprint Story points commited, Sprint Story points added and Sprint story points removed.

P.S. A small correction to my previous answer - "Sprint Story points commited" shows total of SP which are added to the sprint until (not during) the end of the first day of the sprint.

Ilze / support@eazybi.com

All comments

eazyBI Support

Hi Ryan,

in eazyBI, "Sprint Story points committed" measure counts all story points (both resolved and unresolved) at the end of the first day of the sprint; if Story points are added or removed later, they are not affecting a number of committed story points. Read here about Agile measures in eazyBI.

You can click on the committed SP value and drill through issues to see a list of issues which were added to the sprint on the first day, and their story points. If there are some issues missing please write to support@eazybi.com for more detailed assistance.

Ilze / support@eazybi.com

Ryan_tcvdgh

Thank you. When I drill through the issue I see exactly as you describe–the issues that were added on the first day of the sprint.

A couple follow-up questions:

Is the Story Points Resolved measure based on the same "end of the first day of the sprint" commitment?
Is there a way to add story points committed and resolved for issues added after the end of first day?

eazyBI Support

Hi Ryan again,

As, usually, resolved issues are not moved from the sprint, Story points resolved could be used to count resolved story points of the sprint.

P.S. A small correction to my previous answer - "Sprint Story points commited" shows total of SP which are added to the sprint until (not during) the end of the first day of the sprint.

Ilze / support@eazybi.com

Daina Tupule eazyBI

Since version 4.3.0 eazyBI supports committed story points at the moment when Sprint was started.

We also have additional measures for other Sprint Scope changes.

Daina / support@eazybi.com

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core

velocity

report

story-points