When assigning people (resources) in Fixed Work tasks, the program messes up the entire schedule. Instead of keeping work fixed and then adjusting the calendar time in accordance with number of people and their expected allocation (in %), it changes BOTH calendar time and amount work. This is exactly what it should not do. Fixed work means fixed work.
Steps to reproduce
Attached file
Confirming the above, with an attached minimal pod file.
There are 3 tasks (Start, Middle, End) set as Fixed Work / Effort Driven.
Two have resources assigned (50% Andrew, 50% Bertha).
Reproducing the issue
Using v1.9.8 with the attached test.pod, in Task 3
End's blank Resource Names field, type or paste anything that isn't one or more resources at 100%, e.g. step by step as below:Andrew[50%]Bertha[50%]Confirm expected behaviour for 100% resources
Andrew;Bertha(two resources at 100%)Andrew[50%]Notes
Workaround
Workaround in this example file is to initially assign at least one of the required resources (at 100%), then assign fractional / multiple / additional resources as required). The initial resource assignment avoids the issue being triggered, and the subsequent changes to non-100% resources is handled correctly.
However, in a larger file I am using that workaround still triggers the issue, other more consistent workarounds would be welcome! One alternative is to copy the hours column to a spreadsheet or text file, add the resources, then paste the hours back, but that is quite error-prone if any lines were changed during resourcing.
Last edit: Nigel Orr 7 days ago