Calculated Measure for Un-estimated Stories committed to a Sprint

Questions & Answers
1

I’m trying to create a calculated measure to count the number of un-estimated stories that have been committed to the last 5 sprints (or recent history). I was able to create the following report that produces the result I’m looking for by Team. What would the measure look like to give the issue count?

In the example provided, I would expect to see a total of 4 issues of type Story that were committed to the last 5 sprints with a story point estimate of zero.

image
image1122×557 32 KB

2

Hi @Drew_Grant
Thanks for posting your question!

I recommend defining a new calculated measure with the formula below and checking if it works as expected for you?
If you want to create some filters for last closed sprints - you may want to check out this Demo report - Sprint velocity chart - Issues - Jira Demo - eazyBI under the Sprint dimensions you will find several calculated members that you could copy into your report and create some additional Sprint filters

Sum(
  Filter(
    Descendants([Issue].CurrentMember,[Issue].[Issue]),
    [Measures].[Sprint issues committed] > 0 AND
    IsEmpty([Measures].[Issues with Story Points created])
  ),
  [Measures].[Sprint issues committed]
)

Best wishes,

Elita from support@eazybi.com

1 Like