The mockup created to represent ResourceAllocation should return valid values
for methods getIntraDayStartDate() and getIntraDayEndDate().
FEA: ItEr76S04BugFixing
The problem was that when a task finishes in a complete day, that means, task
end date is the next day with zero effort. In this situation, the stretches
calculation was enlarging 1 day more the task itself which causes the issue
reported in this bug.
FEA: ItEr76S04BugFixing
This fix the issue described in previous commit. However, the bug itself is not
fixed yet and needs more work in the stretches function allocation.
FEA: ItEr76S04BugFixing
With this patch the bug is even clearer. If you have a task of 3 days with 8h
per day, and you choose stretches function you will see that the task is
enlarged to 4 days with 6h per day.
FEA: ItEr76S04BugFixing
The mockup created to represent ResourceAllocation should return valid values
for methods getIntraDayStartDate() and getIntraDayEndDate().
FEA: ItEr76S04BugFixing
The problem was that when a task finishes in a complete day, that means, task
end date is the next day with zero effort. In this situation, the stretches
calculation was enlarging 1 day more the task itself which causes the issue
reported in this bug.
FEA: ItEr76S04BugFixing
This fix the issue described in previous commit. However, the bug itself is not
fixed yet and needs more work in the stretches function allocation.
FEA: ItEr76S04BugFixing
With this patch the bug is even clearer. If you have a task of 3 days with 8h
per day, and you choose stretches function you will see that the task is
enlarged to 4 days with 6h per day.
FEA: ItEr76S04BugFixing
The problem was that ResourceAllocation.DayAssignmentsState has a wrong start
day for consolidated tasks.
During the consolidation the method used to do the reassignment called
ResourceAllocation.allocateTheWholeAllocation which changed DayAssignmentsState
start date to first day not consolidated. Now this method is avoided, and the
start date in DayAssignmentsState is right.
FEA: ItEr76S04BugFixing
The problem was that ResourceAllocation.DayAssignmentsState has a wrong start
day for consolidated tasks.
During the consolidation the method used to do the reassignment called
ResourceAllocation.allocateTheWholeAllocation which changed DayAssignmentsState
start date to first day not consolidated. Now this method is avoided, and the
start date in DayAssignmentsState is right.
FEA: ItEr76S04BugFixing
New folder with link to different documentation files in the source code. It
also includes a script to generate the HTML files that will be available on-line
at http://libreplan.org
FEA: ItEr76S03Community
New folder with link to different documentation files in the source code. It
also includes a script to generate the HTML files that will be available on-line
at http://libreplan.org
FEA: ItEr76S03Community
The issue was introduced in commit a998367bec
while trying to fix a different problem in interpolation function.
The patch has been reverted and both issues fixed now.
Once the patch was reverted, the number of remaining hours was wrong calculated
as if it was 0 it returns the allocated hours instead of 0.
FEA: ItEr76S04BugFixing
The issue was introduced in commit a998367bec
while trying to fix a different problem in interpolation function.
The patch has been reverted and both issues fixed now.
Once the patch was reverted, the number of remaining hours was wrong calculated
as if it was 0 it returns the allocated hours instead of 0.
FEA: ItEr76S04BugFixing
The derived day assignments were not being included. This caused that
the resources associated with the derived allocation to have different
instances for the derived allocations, causing a subsequent error.
FEA: ItEr76S04BugFixing
The cause of the bug was that IntraDayDates were converted into Date objects,
and then back again to an IntraDayDate with 0 EffortDuration.
FEA: ItEr75S04BugFixing
The cause of the bug was that IntraDayDates were converted into Date objects,
and then back again to an IntraDayDate with 0 EffortDuration.
FEA: ItEr75S04BugFixing
The advance bar was always drawn until the end of the day, even when the task
finished in the middle of the day, causing a weird effect.
FEA: ItEr75S04BugFixing
The advance bar was always drawn until the end of the day, even when the task
finished in the middle of the day, causing a weird effect.
FEA: ItEr75S04BugFixing
