Hi @ruaghain,
eazyBI provides several Sprint scope related measures out of the box: commitment, changes, and what is delivered at the end of a Sprint (https://docs.eazybi.com/eazybijira/data-import/data-from-jira-and-apps/jira-software-custom-fields)
You may use those measures for defining the new calculated measure to get story points that were committed to a sprint AND also completed in a sprint might look like this:
Sum(
-- filter all issues which were committed and completed
Filter(
Descendants([Issue].CurrentHierarchyMember, [Issue].[Issue]),
[Measures].[Sprint Story Points committed] > 0 AND
[Measures].[Sprint Story Points completed] > 0
),
-- sum up completed SP
[Measures].[Sprint Story Points completed]
)
The calculation goes through issues and validates each, whether it was committed and completed for a selected sprint.
Our partner, “demicon GmbH”, demonstrated an excellent use case on Sprint scope analysis Better SAFe than Sorry - Enterprise Ready Reporting at Scale in Jira that might interest you. The video of this and other talks from eazyBI Community Days 2019 are here: Presentation slides from eazyBI Community Day 2019 in Riga
A similar use case to count story points that were committed and not completed in a sprint is described in another eazyBI Community post: Missed Commitment Report in EazyBI
Best,
Zane / support@eazyBI.com