Hello there,
Please help with a report that will show the difference between the estimated and actual sprint hours for each person, is it possible to implement this with the resources of Jira, or do I need some additional plugins?
Regards,
Hi @Anton_kolesnyk
Welcome to the community!
Please refer these which was asked before:
https://community.atlassian.com/t5/Jira-questions/Chart-to-show-estimated-time-vs-actual-time/qaq-p/669185
https://community.atlassian.com/t5/Jira-Software-questions/Sprint-Reporting-Planned-Vs-Actual/qaq-p/1807947
Hope this helps.
Thanks,Vamsi
Hi, thanks for the welcome, I have already read the advice above and tried to configure it through the dashboard, but I am interested in the implementation through JQL or tables, is it possible to search by person in the sprint so that I can see the difference between the estimated and actual sprint hours?
Thanks,
Are your hours the sprint statistic? Feeding into the sprint's velocity?
Actually what I am looking for is a way to pull estimated hours vs logged hours per each ticket. This info is needed to asses estimations accuracy. Could you please give me a hint on how it could be done ?
Jira does not have a per-user report like this (because it's not how you should be doing scrum, and it's actually illegal to do user monitoring like this in some of the marketplaces (countries) that Atlassian sells into). The closest you can get is a "workload report", from the project's reporting panel, which is aimed at showing you who is currently over or under loaded with work so you can re-allocate if necessary.
Measuring it by issue is, of course, absolutely fine, so it then comes to what report you actually want from it.
The most simple one would be the issue navigator, where you can run a search for a pile of issues , and choose to display the ΣOriginal Estimate, ΣProgress, ΣRemaining Estimate and ΣTime spent fields (I use the Σ fields so that I can ignore sub-tasks in non-agile projects).
But I quite like putting in a calculated field for "estimate variance". I don't use anything as simple as this, but if you create a numeric field that contains "ΣTime spent * 100 / ΣOriginal estimate", you get a ratio (a simple percentage) that can be easily sorted and searched to find issues that went under or over. It's much the same as the progress field, but easier to report on, and I only calculate it for "done" issues (resolved)
It looks like you're new here. Sign in or register to get started.
