Measures of Sprint Story Points Added/Moved

Hi there,

We have been tracking Sprint story points changes in EazyBI, it is great that there are pre-defined measures already for them, but the problem is in our teams, story sometime got added into Sprint by mistake (create new story from copying old one with current Sprint value and removed in the same day). We want to exclude this kind of changes in story points added/removed measure. Can you please advise how to modify the measures to get what we expect? Thank in advance!

—Sprint story points added—
( [Measures].[Story Points added],
[Transition Field].[Sprint status],
[Issue Type].[Requirement/User Story],
[Sprint Status].[Active],
[Issue Sprint Status Change].[(none) => Active]

—sprint story points removed—
( [Measures].[Story Points removed],
[Transition Field].[Sprint status],
[Issue Type].[Requirement/User Story],
[Sprint Status].[Active],
[Issue Sprint Status Change].[Active => (none)]

Hi @Sasha_121937,

Sprint scope measures look at adding to and removing from Sprint activities separately. You may create a calculated measure that would go through individual issues and check on both actions and, based on that, sum up the story points. The structure for calculated measure might look like this:

  --set of issue
    DescendantsSet([Issue].Currentmember, [Issue].[Issue]),
    NOT IsEmpty([Issue].CurrentMember.Get('Sprint IDs')) 
    --check issue was not removed from sprint
    IsEmpty([Measures].[Sprint issues removed])
   -- sum added story points
  [Measures].[Sprint issues added]

And similar expression for removed story points, but then check if issues were not added to the sprint.
Such calculations are resourceful and might impact report performance.

An alternative is to clean up data. For example, consider automatically clearing the Sprint field when cloning or moving issues in Jira. Or adjust data for cloned issues and clean the sprint history using JavScript during data import in eazyBI (Data adjustments using JavaScript).

Zane /