none
Future Actual Hours & Future Actual Finish Dates RRS feed

  • Question

  • Hi All,

    I am using Project Server 2015 Jun 2015 CU. We are using single-entry mode, actuals are only allowed from the timesheets, and future time reporting is not allowed.  

    We are seeing assignments (project -->task-->resource) where 0 hr hours are entered well out into the future, as much as by 50+ years! Since the system has 0 hrs entered every day until that new end date, the project manager is unable edit the end date to the task, as the system sees those 0 hrs as protected actuals.  Sometimes there is remaining work, and other times there is no remaining work, so it doesn't appear to be due to the process of closing or completing a task.  While I have been able to find a work around, I am still looking for the cause!  I am also looking to see if there are others out there who are seeing the same issue.  

    The workaround I have found to repair the issue is through using the Tasks.aspx page. If I go in as a delegate, select the task with the future finish date, edit the end date of the task to the last working day of actual hours on the timesheet. Save on the task page, and then submit that one task for update to the PM. Have the PM approve and publish. Usually this will pull the end dates back in, though in one case, I had to add 1 hour in the schedule, then remove that 1 hr and it updated correctly. I do not have the resources take these steps and have been doing it as an admin delegate and while it is working, it is just a bandaid.

    Has anyone figured out where these issues are beginning? It seems to be happening to PMs and resources alike!

    Any help or updates would be appreciated! I have working on testing the May 2016 CU, but so far, I am not hopeful that the issue has been resolved.


    Wednesday, June 8, 2016 1:49 PM