Timesheet roundup–over on Project Support

A couple of recent posts over on Project Support cover some behaviors in Project Server timesheets that can catch folk out.  The first relates to deleted projects and assignments – and what then happens in the timesheet – Project Server Timesheets- What happens when I delete a project or assignment- – as well as covering a bug in 2013 where the timesheet status is getting reset when a status approval follows a timesheet approval (which is virtually every time when you self approve timesheets!  Then the 2nd came out of comments made on the first – and covers the relationship between assignments and timesheets – and the fact that one assignment can span multiple timesheets – and if there is time to submit on more than one of these – then guess what – it gets submitted too! Timesheets and assignments–updating status isn’t just for the current week 

These apply to Project Server 2010, Project Server 2013 and Project Online.  Thanks to Gary, Treb and Elli for their input into these conversations.  And yes Gary, I’m still looking into a script to resolve the ‘wrong status’ issue.


Comments (4)

  1. Marilyn Bliss says:

    Any update on this issue?  We just recently migrated from 2010 to 2013 and now our Timesheet Status report from the DB no longer matched the Manage Timesheet status in the PWA website.

    Looking for any information please,



  2. Hi Marilyn, the specific status difference issue was resolved in the June 2014 update – When you approve a status update in Project Web App, the status of the associated timesheet as seen in the reporting database changes unexpectedly – support.microsoft.com/…/2881062 – but I am aware of another scenario where you use auto approval and submit status update that go to different status managers at the same time can set one of the lines back to waiting for approval.  Does that sound like it could be your issue?  Or do you need to load June update or more recent?

    Best regards,


  3. Marilyn Bliss says:

    Thanks for answering so quickly Brian as this issue is causing doubt in our reporting ability amongst our leaders.  We are currently at March 2015 CU so we are not sure why this is happening.  We simply updated an odc file to the new DB Server and while doing a quality check against our timesheets and the report we found that the status in the DB didn't match what was listed under the Manage Timesheets page.  We then looked at all our timesheets that were approved before migration and they are now set to Not Created or Null in the DB but still appear as approved in the new environment Manage Timesheets page.  We are using Auto approve.  Another thing we noticed is that hours entered on timesheets are not appearing in the project plans either.  Something seems out of sync.

  4. I'd suggest opening a support incident Marilyn so we can dig deeper.  You should review the approval history to see if any issues occurred while the approval was being applied – and we'd also need to better understand the nature of your migration as it seems like some timesheet metadata messed up on the way across.

    Best regards,