Difference in reports from Jira to Eazybi

I’m evaluating EasyBI and am using the default reports in the jira box. Did something which should be simple, but I can’t figure out what I set up wrong. My teams are adding multiple stories after start of sprint and I want to track this, however the measure Sprint Story Points committed and Sprint Story Points commitment changes are not showing what Jira is showing me. The easiest way to show this is with the following diagrams

They are burn up and burn down, but the issue can be seen. Jira is showing the story points as starting at 6, where easybi is showing 46.

I have the following import configurations

which according to what I’ve found should work.

Any thoughts on why the history appears to not be working.

I would you to recommend to compare the data in both sprint report and eazybi table.

  1. Sprint goal
  2. Sprint Story Points Comitted
  3. Sprint Story Points added
  4. Sprint Story Points removed
  5. Sprint Story Points Change
  6. Sprint Story Points Closing
  7. Sprint Story Points Completed
  8. Sprint Story Points NOT Completed

The equation looks like this for me
Sprint Story Points Closing = (Sprint Story Points Comitted+
Sprint Story Points added-Sprint Story Points removed+Sprint Story Points Change)

Sprint Story Points Closing =
(Sprint Story Points Completed+Sprint Story Points NOT Completed).

This is just to rule out any issues in configuring reports or eazybi fields.
Best of luck.


Your observations are correct - sometimes, data in eazyBI and Jira are different because of approach of how data are calculated. eazyBI imports issue information, not pre-calculated report data from Jira reports.

Let me explain how eazyBI calculates those measures.

Measure " Sprint Story points committed " sums up story points assigned to a sprint at the moment when the sprint was started (button [Start sprint] was pushed). This value includes Story points in all statuses, also resolved before the sprint was started.
Committed points can’t be changed by removing/adding issues later or changing story point values: committed points value is a snapshot of that exact time moment.

Measure " Sprint Story points completed " sums up story points from completed issues at sprint completion moment. Issue story points are treated as completed if the issue was in one of the status category Done statuses at sprint completion moment. The board configuration (a column mapping to statuses) is not taken into account for this measure.
Therefore, if your sprint board configuration is different (the last swim line in the board - Completed - contains issues in other statuses, not those from Done category), you may create your own calculated member, where you use your statuses instead of category Done:

Sum (
{[Transition Status].[STATUS_NAME1],
[Transition Status].[STATUS_NAME2]},
[Measures].[Sprint Story Points at closing] )

I would suggest comparing committed issue lists from both, eazyBI and Jira, and then find issues with differences. Check their change logs for when those issues were added to sprints, when story points were added or changed, etc.
The same for completed, what was the status of completed issues at the closing moment of the sprint.

Please find more on sprint scope measures here: Jira Software custom fields - eazyBI for Jira

And find this documentation page on how to build sprint report in eazyBI:

Martins / eazyBI