Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can demonstrate our sprints completion rate?

In EazyBI, I want to create a chart that lists our sprints, and then shows for each sprint:

  1. The Number of open tickets that were part of the sprint when the sprint was started
  2. The Number of resolved tickets that were part of the sprint when the sprint was closed.  This would not include tickets that were removed from the sprint after it was started, but would include tickets that were added to the sprint after it started.
  3.  #2 divided by #1 - the percent of the original planned sprint that was actually completed during the sprint
  4. The same measures but summing "original estimate" - as in, the total # of hours committed to and then completed, and the % completion rate based on the estimates.


Once I can do this for the whole team (demonstrating the sprint-by-sprint success ratio for the team), I would want to create the same graphs per person to see what each team member's success rate is.

What is the best way to accomplish this?



1 answer



Together with Mattew, we got those measures:

1) To get "Sprint committed issues", calculated measure should be created:


  [Measures].[Issues history], 
    [Sprint].CurrentMember.get('Start date'))


2) For Sprint resolved issues, standard measure "Issues resolved" could be used.


3) To sum up estimates from committed issues, calculated measure could be the following:

    Descendants([Issue].Currentmember, [Issue].[Issue]),
    [Measures].[Sprint Issues Committed] >0),
    [Measures].[Original estimated hours]))


Be aware! As this measure iterates trough all issues and their changelogs, it is quite slow, therefore, should be used only for one or a few sprints selected in the report!


4) For Sprint resolved estimated hours, the measure could be the following:


(([Measures].[Original estimated hours],


where  [Resolution].[Resolved] is a calculated member in Resolution dimension with aggregated all resolutions except (unresolved).


5) For ratios, measures with divisions between needed calculated measures were created.


Ilze, eazyBI Customer support consultant


Suggest an answer

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

Happy New Year and Welcome New Marketplace Partner Program Partners!

Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...

840 views 8 25
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