In our project we use time estimate instead of Story points. Not the best I know.
And there are some issues I don't understand and I can't fix:
- I have a task with 2 sub task with 1d for the first one and 1h for the second.
After wrong time log, eventually I have a remaining of 1d 1h and a remaining sum of 2d 2h. How the remaining sum can be more than the remaining? How can I fix it to have a remaining sum of 1d 1h ?
See Screenshot below
- Initially, estimate time was wrong. We've changed it.
In the Active Sprint board, changes have been updated. But in the backlog the estimate has not been updated and is not accurate. see below:
=> How can I change the remaining sum to be the same as the remaining and how can I refresh the Backlog estimates?
Hello @Yorann Baron ,
The value for "Remaining" is the "Estimate" value minus time "Logged " just for the parent task alone, where the "Remaining Sum" is a summation of remaining on the parent + remaining on the Sub-tasks combined.
So looking at the screenshot of the issue the parent has an estimate of 3 days and it looks like time has been logged on the parent to reduce the parent issue to "1d 1h", (if days are set to 8hours that would be 15h of work logged on the parent issue) then the subtasks combined would have no work logged and still contain 1d and 1h respectively on the two subtasks if that was the case.
Can you check the work log of the subtasks compared to the work log of the parent to verify if this is the case?
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events