2024R2.4 - Resolved Issues

A bug caused Resource allocations prior to substitution dates to be erased after users performed a substitution on a Project Work Plan. This occurred specifically when Replace assignments after a specific date was selected from the "What assignments should we replace?" menu.

When the replaced Resource then acted as a substitute for another Resource after the exact same date, the Resource would lose their original allocation before the replacement date. This occurred even when Keep assignments (reduced 0%/0h) was selected from the "What should we do with the replaced resource?" menu.

Example: Jack is assigned to a Project Task that lasts from April to December. However, a substitution caused Tim to replace Jack on the Task after May 31^st. This means that Jack remains on the Task until the end of May. This worked as expected.
However, Cristina was assigned to another one of the Project's Tasks with the exact same duration. She is substituted as well, this time with Jack as the replacement after the same date: May 31^st. Jack is expected to keep his allocation to his other Task prior to this date, but it is erased.

This bug has been resolved; substitute Resources will no longer lose their allocations prior to the replacement date.

A bug caused the Resource Time report to display incorrect data after taking Project Baselines. Allocation percentages, actual time, and Start / End Dates were inaccurate when the report was run through the Excel Add-In.

An investigation into the issue revealed that essential information was not being captured during report execution. As a result, some data was duplicated in the output, leading to inaccurate and inflated figures.

This bug has been fixed; the Resource Time report will no longer display duplicated and inaccurate data when run through the Excel Add-In.