TimephasedResourceAssignment end date not correct
Multi platform library to read and write schedule data
Brought to you by:
joniles
Hi,
I am using release mpxj-3.1.0 and noticed an anomaly with dates that use the TimephasedResourceAssignment. Attached is a small mpp file that contains a TimephasedResourceAssignment where the total effort for the assignment is equal to 64 hours (as seen in screenshot1.jpg)
Screenshot from Project
Sample Project File to use to replicate issue
Small Java App that replicates the issue
Sorry continuing description... Posted before completed description.
When the TimephasedResourceAssignment is parsed in the attached PAYG.mpp project file it shows only a total planned effort of 56 hours. It appears the final TimephasedResourceAssignment has an end date of the 16th Jul when it should be the 17th Jul.
I've just released version 3.2.0 - would you be able to check to see if this is still an issue?
Thanks!
Jon
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Hi Jon,
Just checked with 3.2.0 and it's still an issue.
Hi Jon,
Sorry logged in with my google OpenID. Anyway, just tested it again with 3.2.0 and it still appears to be an issue.
Cheers
Brendan
I've tested this with the code now in CVS, and everything appears to be working as expected. Points to note: 1. The timephased work API has changed since this bug was raised. 2. Note that the timephased data is split between actual work, and planned work, and you'll need to look at both lists to get the complete picture (in this example the 64 hours of work for the test assignment is made up of 8 hours planned, and 56 hours actual, which you will see split across the two lists of timephased data)