After a sprint has closed I would like to run a simple report that shows the hours spent compared to the original estimate. The issue here is that unless I put in a timeframe that extends beyond the current sprint to include the “timeframe” of when the issue was originally created I don’t get the original estimate.
This is a problem because some issues are created well in advance and estimates applied well in advance of assigning to a sprint. How can I obtain the original estimate of hours without expanding my timeframe beyond the 1 previous sprint?
Thanks for your question!
The measures Original estimated hours and Remaining estimated hours are counted only against the issue current sprint. And because of this, it looks that some issues are shared between several Sprints so they don’t appear in your report when you select specific Sprint, otherwise, it should show you Original estimated and Remaining estimated hours.
But checking what you want to see, I think that one report from our eazyBI demo account could be almost exactly what you are searching for - Sprint time tracking . The report is built based on Remaining estimated hours which resembles original estimation at the beginning and changes over time when logging hours or estimates are updated - https://eazybi.com/accounts/1000/cubes/Issues/reports/93784-sprint-time-tracking
It is using very similar measures that we have described based on Sprint Story points, see more here - https://docs.eazybi.com/eazybijira/data-import/data-from-jira-and-apps/jira-software-custom-fields#JiraSoftwarecustomfields-Sprintscopemeasures
You can easily export and import this report definition into your account and then change it accordingly to your needs.
Also, there is one more demo report about time tracking in Sprint that you might find relevant to you - Time Tracking Burndown in Selected Sprint https://eazybi.com/accounts/1000/cubes/Issues/reports/144076-time-tracking-burndown-in-selected-sprint
I hope this will help you with your case!
Gerda // eazyBI support