Monday, March 14, 2016
1 change · master
Code cleanup and technical improvements
This update improves how timesheet-related project tasks calculate delays and total hours, fixing cases where delays always appeared as zero. It also streamlines task behavior to reduce confusing automatic changes, making project progress and workload reporting more reliable.
Original PR description
Description of the issue/feature this PR addresses:
\* New API migration
\* Fix delay hours and total computation : Delay was wrongly computed as 0.0 in every case. This should be fixed now.
To be discussed :
\* The field total_hours could probably be removed.
EDIT: It will be the max between planned and effective hours
\* Why do we set tasks to 99.99% instead of 100% ? It seems more historic than logic.
EDIT: It is actually intended to have tasks at 99.99% instead of 100% as long they are not in a folded stage.