I am observing a mismatch between completed story points as observed in JIRA and EazyBI. Eg. In JIRA, project Velocity chart display 11 completed story points but EazyBI display 18 Story points. The formula applied is working correct for other projects but not getting exact data for this project. Can anyone please help to find a solution for the same.
I am not able to find the extra issues responsible for generating extra completed story points, due to time out in query execution by EazyBI, it is getting difficult to detect the issue.
In case any one has experienced the same issue, your help would be appreciated.
eazyBI doesn’t reflect the same configuration as the particular Jira board in which you observe the completed story points mismatch. In eazyBI, the story points from issues that were in any Status of the Jira Status category “Done” at the time of Sprint closing are considered completed.
The particular projects board configuration may differ from the one eazyBI uses. To overcome this, you can try to create a new calculated member in the Transition Status dimension that reflects this configuration. The formula could look similar to the one below:
-- Completed Statuses
Then you can create a new calculated measure to get the number of story points at the time of closing of the Sprint in those statuses:
[Measures].[Sprint Story Points at closing],
[Transition Status].[Completed Statuses]
You can have a look at the eazyBI documentation page for more information on the Sprint measures - https://docs.eazybi.com/eazybijira/data-import/data-from-jira-and-apps/jira-software-custom-fields.
Also, you can have a look at this presentation from our partner, Demicon at the eazyBI community days in 2019 regarding Sprint scope analysis - https://eazybi.wistia.com/medias/gq751ooyck?wvideo=gq751ooyck.
Roberts // email@example.com