I have some tasks with set time constraints. Those tasks are A, B, C. Dependencies: A -> C B -> C I had started few (A, B) of them earlier than what the scheduler suggested, and I also finished them earlier. Scheduler should reschedule task C such that it could start earlier. Gantt chart should show the real, actual start, finish times of tasks, not the computed ones. Link to a Calligra .plan file showing the bug: http://wyslijto.pl/plik/0mhex9px10 Link to the KDE forums: http://forum.kde.org/viewtopic.php?f=203&t=110291 Reproducible: Always Steps to Reproduce: 1. Create three tasks A, B, C. 2. Set dependencies: A -> C, B -> C. 3. Set reasonable time constraints of type 'As soon as possible' for each of them. 4. Schedule tasks. 5. See on the Gantt chart that everything is ok. It's ok. 6. In the task execution, set task B so that it started a few days before the constraints interval. 7. In the task execution tab, set task B so that it finished a few days before (earlier than) the constraints interval. 8. Schedule tasks with the scheduler. 9. Go to the Gantt chart and see that task B is incorrectly displayed. Task B is shown as it didn't finish earlier than the constraints interval and computed values of the scheduler. Actual Results: In step 9 I see an incorrect Gantt chart: Task B is shown in the dates range computed by the scheduler, not in the range of dates when the task has been performed in reality. Expected Results: In step 9 I should see a correct Gantt chart: A chart that would display task B some days earlier - when it actualy started and finished. Link to a Calligra .plan file showing the bug: http://wyslijto.pl/plik/0mhex9px10 Link to the KDE forums: http://forum.kde.org/viewtopic.php?f=203&t=110291
Created attachment 78199 [details] Calligra plan file showing the bug
I confirm Task completion do not have any effect on actual planing in calligraplan :(
You can add a sub-schedule to your schedule and reschedule the project. It will then take finished tasks and remaining effort into account when scheduling.
*** Bug 320179 has been marked as a duplicate of this bug. ***