Hi there,
I've read a lot of posts but cannot see a clearly defined solution for this issue where the time remaining on a Jira project isn't calculating correctly.
Example shown below.
The order of the columns are: Time Spent, Original Estimate, Remaining Estimate.
The graph on the right hand side represents the overall time tracking.
The amounts shown as logged, is correct. However, the time remaining is not correct because you can see in the second row 23.75h have been spent of the original 10h. The delta of 13.75h is represented correctly in the graph.
So, if you do the math the total Original Estimate = 123h minus Time spent 85.83h should equal 37.17h.
Any help would be greatly appreciated.
Thanks,
Gary
Hello Gary,
The original estimate is not represented in this graph. The simplest explanation is:
I hope this helps! It’s not really intuitive, I agree.
Cheers!
Hi Wojciech,
Thanks for that.
Yes, you're right the orange represents 13.75h over original estimate. However, what I was hoping for was the Remaining Estimate column to go into negative by 13.75h.
Which would then mean that the graph should display 37.17h, which takes into account the total time spent across all tasks, including those that have gone into the negative to give the overall time remaining for the project.
Thanks,
Gary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gary,
A negative value of 13.75 in Time remaining, both in practice and by definition, would mean that someone has to return to you the 13.75 you spent on the task. Such a situation doesn’t exist in the real world.
Remember that Time remaining refers to the current remaining time and is not connected to the Original estimate.
The Original estimate refers only to the initial estimation and is not really related to the current remaining time.
That’s how it works from the business side. What you're looking for is more like a field showing the relationship between the initial estimate and the remaining time — but such a field doesn’t exist. It’s only represented visually as a color on the progress bar.
However, if you’d like to implement something like that, you could try using Automation Rules or, for example, Scripted Fields (a part of ScriptRunner).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Wojciech,
Thanks again for the detailed explanation. That makes sense and I understand why a negative value in “Time Remaining” isn’t realistic in Jira’s current model.
However, in real terms, when we’re working to a fixed consulting budget, say 40 hours across a project, and a particular task (eg. consulting) is estimated at 10 hours but ends up taking 15, that overrun eats into the overall project allocation. It would be really valuable to reflect this at an aggregate level, so we can see where we’re trending over budget in specific areas.
Are there any examples you could point me to for how others have implemented something similar, perhaps using Automation Rules or Scripted Fields to surface this relationship between actual effort and initial estimate more clearly? I’d love to explore a way to represent this more transparently, even if it’s via a calculated field or a report view.
Appreciate your help so far.
Best regards,
Gary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gary,
You are right, such situtation happens and you can track it in jira, but you should use more aggregation tool, than try to display it on the particular work item. I would recommend you to use Time Tracking Report (project report). At the end you have summary and data which you need. If you want to split data (into packets of hours, for example) then doing so from the Version functionality seems sensible.
If we are talking about Automations or ScriptRunner (additionally paid) we have to calculate:
"Original estimate" - "Time remaining" = X
With Automation Rules:
Something like that should help (we are calculating for field Serial Number). Smart Value in the "Create variable" is:
{{ issue.timetracking.originalEstimateSeconds | minus(issue.timetracking.remainingEstimateSeconds) }}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.