Hello,
I hope everyone is keeping well !
I am trying to get my remaining estimate hours history measure (or different calculated measure) to take into account hours spent on sub-tasks so that my burndown chart is showcasing data right.
As you can see below I have 10.5h then 6h from sub-task and then my remaining hours are still 10.5h - which makes my burndown chart not correct.
I am trying to create a burndown chart using - Time Tracking Burndown in Selected Sprint - Issues - Jira Demo - eazyBI
Hi @Andrzej_Paszek ,
The main problem with logging hours on subtasks and tracking original estimates on the parent issues (story) level is that these are independent values.
When logging time against an issue, you have the option to adjust the remaining estimate on that issue level. Otherwise, the remaining estimate is automatically reduced by the amount logged.
However, when you register the hours against the child issue (sub-task), there is no estimation to be adjusted. The remaining estimate on the story level is not impacted.
The option of subtracting the hours spent on sub-tasks from the original estimate on the parent level might not work, as the hours spent on sub-tasks can easily exceed the estimate of stories, like in the case of FH-677, where the original estimate was 10.5 hours, 4 hours were logged against the story, and 10.08 hours against the sub-tasks, leading to -3.58 hours remaining.
As the hours logged and remaining estimate updates are not synchronised, the measure “Remaining estimate history” cannot work on your setup.
Regards,
Oskars / support@eazyBI.com
