Sprint Story Points vs. Sprint Estimated Story Points

Hi @davide!

eazyBI uses the Jira Software field ‘Story points’ to create Sprint scope change measures, see more here Jira Software custom fields.

Nevertheless, you can import any custom numeric field value changes and from there write an MDX function similar as in “Sprint Story Points committed” to see what the value of the field was at Sprint start. From your example, the ‘Estimated Story Points committed’ formula should be as follows

( [Measures].[Estimated Story Points history],
  [Transition Field].[Sprint status],
  [Sprint Status].[Active],
  -- An issue was in a sprint at a sprint start time
  [Issue Sprint Status Change].[Future => Active],
    [Sprint].CurrentMember.get('Start date')

Also, use the “Estimated Story Points history” measure that is created when importing value changes to see how the value of the field changed during Sprint time.

Lauma / support@eazybi.com