Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

EazyBi - sprint original estimate at closing


Hi! I have been challenged to create specific report for my team. We're using original estimated hours field in order to plan workload, so the value of this estimation has more less same meaning for us as story point. Now I want to catch this estimation value and group it by issue status at the end of the sprint - so practically I'm looking for something similar to "Sprint Story Points at closing" but for Original Estimated Hours.

Just to complicate it a bit i tried to create calculated member formula to count this value for example for issues in progress, so in my case with status "In development" or "Code review".



    Descendants([Issue].Currentmember, [Issue].[Issue]),

    [Measures].[Issue status] matches ("In Progress|Code Review")



    [Measures].[Original estimated hours],

    [Logged by].DefaultMember



and as you can see my problem is with issue status when I try to use this formula for closed sprints, because it takes current status and not historical one (so at the moment of sprint closing).

So my question is: am I close to the solution of my problem or should I approach subject differently? 

1 answer

1 accepted

1 vote
Answer accepted

Hi Robert,


You are right, using that formula the calculation would filter issues by the current status which is not what you need in your case.

Try this formula:


Descendants([Issue].Currentmember, [Issue].[Issue]),
[Transition Status].[In Progress],
[Transition Status].[Code Review]
[Measures].[Sprint issues at closing]
[Measures].[Original estimated hours],
[Logged by].DefaultMember


Martins / eazyBI support

Thanks Martins - that's what I was looking for!

Now the total numbers are ok, but what's weird now I have some huge performance issues when I'm trying to show those numbers for each assignee. Could it be connected with complexity of this formula?


Yes, this is a complex calculation.

When selecting this measure make sure that "Nonempty" cross join is enabled for your report.

Martins / eazyBI team

Like Calogero Kalos Bonasia likes this

Thanks Martins, that helps a bit. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

336 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you