Story Points Resolved returning double the story points

Hi Folks,
We have run into an interesting anomaly.

Using the “Story Points Resolved” Agile Measure we are seeing double story points being claimed. That is, if the ticket has an assigned Story Point value of 5, the “Story Points Resolved” measure is showing 10.

What could be the cause for the unexpected results?

One of the most probable options might be using multiple selections or calculated members in the report for a dimension with multiple values, like Fix version, Labels.
In the example with Labels. If you have labels A, B, C selected in the report on Pages. eazyBI will count issues with two labels (for example, a and b, b and c, etc.) twice.

You can use issue level calculations to avoid this:

    Descendants([Issue].CurrentMember, [Issue].[Issue]),
    -- filter by time
      [Measures].[Issue resolution date],
  -- validate if you have story points
  [Measures].[Story Points resolved] > 0
  -- use property as counter
  [Measures].[Issue Story Points] 

Daina /

Hey Daina,

I am having a similar issue, I am trying to get all of the closed story point by Epic. If I switch to using the value from issue then I correct the correct number on a ticket by ticket basis, bit when I switch to “Total Story Points” on the Epic and if the Story meets more than one criteria, for example it sits in multiple fixVersions or multiple components, then the story point value get’s multiplied for each hit.

I tried adding the measure you suggested above but my system times out and I can’t get the results, I don’t suppose you have any other clever ways I can get around this? :slight_smile: Thanks.

Yes, you are correct. The formula I shared might work slowly. However, when dealing with multiple-value fields you would like to use issue-level calculations to get the unique values. Issue-level calculations could work slow in reports with some other complexity and/or in accounts with a large number of issues.

Please check if there is an option to reduce the imported number of issues in the account or move the report to the account with fewer issues. We suggest working with many but small accounts to get the desired performance.

You can check these suggestions for best practices in report creation to make sure the report has minimal added complexity.

Please note. The current formula is quite general. There could be the option to add some additional filters to get it working better for a specific report. If the suggestions above do not work, You can send a report definition to and ask for assistance on the report.

Daina /