Closed ydelgadoplata closed 1 year ago
In genereal the system is designed to calculate remaining time
for a task by multiplying %done
with estimated time
.
Why? We want to differ between "estimated" and "reality". In everyday-work we sometime need more or less time on a task than we estimated.
If we would calculate estimated time
minus booked time
we could not calculate remaining workload properly.
Or we would have to edit our estimated time
with some calculations regarding remaining time
. But than we could not see the difference between estimation and reality.
As far as I know all project-management-tools work that way as we do it here.
Out there are Plugins that e.g. calculate EVM.
They also rely on this methodology (multiplying %done
with estimated time
/ keeping estimated time
untouched).
@mboremski I think you're right. I've also configured the %done
to change automatically with the status
of the task, so I'm actually updating the statuses in order to validate the correct status of the tasks. It seems to work for me and for what I need to do.
Thanks a lot for the clarification!
Glad to read your reply. Will close this one.
Greetings development team!
There's an idea circling on my mind and is about updating the workloads of each member, taking into account the spent time reported per issue/task per day.
For example, to calculate the workloads the Start, end and estimate time need to be filled, but I noticed that if I report 1 hour of spent time for one of the tasks/Issues I have assigned, the workload is not updated. Instead of updating the workload, the workload is getting increase.
It would be really great, if the workload is updated taking into account the spent time per each issue/task. In this way, me, as a Project Manager, could decide which member of my team have less or more workload in order to assign or reduce work.
Thanks for your attention and please, let me know if this could be possible to make a reality, it will help us a lot!
Best Regards!