I think using EazyBi for this is being overly complex. Why not just use the built Agile burndown charts? You need to specify a start and end date for your release and then you'll get a velocity line with a projected end date.
If you're set on using easy BI, have you started with some more basic concepts? I need a report to break out productivity by team. I used the custom numeric field "LOE closed" (I think this was supplied by my particular version of JIRA, not created by me) with rows "Sprint" and "Issue". This allowed me to plot LOE closed per team sprint. If you want to provide the estimated number of sprints left based on velocity you would probably need to change what I have in "Pages" from "Project" to "Fix Version".
Sorry it's only slightly related, but hopefully it gives you some ideas.
You can take a look on example report "Sprint velocity chart" in eazyBI demo account: https://eazybi.com/accounts/1000/cubes/Issues/reports/61946-sprint-velocity-chart.
There is used a calculated measure "Running velocity for 5 closed sprints" which calculates the average velocity based on last 5 closed sprints. You could create a similar measure in your account or even use this report as a base for yours (then export it and then import to your account).
For assistance with "Estimated number of sprints left based on velocity" and further report elaboration, please, contact email@example.com and describe how this metric should be calculated.
Ilze, eazyBI Customer Support Consultant
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs