A bug in 2013 causes the timesheet status to reset in the reporting database when a assignment status approval (Project Manager) follows a timesheet approval (Timesheet Manager). If your users approve their own timesheets this error occurs with every timesheet submission. A second bug occurs when one assignment spans multiple timesheets, and the user enters actual time to more than one period, in this case submitting one incorrectly submits the other. Brian Smith posted a series on this, start with the most recent (http://r20.rs6.net/tn.jsp?e=001GeMdxjO1pN2bBX5PlKkmbx4HgDfS8J_O4f3plPfvIjst0qIzarm6ohBI5-QlyraVHBBhds0pV7GDa3zOSU7duphwgAoN5BUE-8jAFy3UK_8ip4O-Sk47X2GBMb3UlisIYeE3O9EmGX0sN7jEoSKyVXH1xgBs5wWaqpDLBgWwddoGPaNqWYL4q0h3YTOBrvg4MGm9UfGy5jmGbbrUpFxUi_9SSJvcoWZDB0PcjsJUMKU=). Read on to discover good explanations of other vexing timesheet behaviors in both Project Server 2010 and 2013.
Articles in this section
- Office 365 Quick Start Guide
- Can I run Microsoft Project Professional on a Mac
- How to add team members or users to SharePoint site?
- What to try if you can't IM Lync or Skype external contacts
- How to uninstall Office 2013 or Office 365
- Timesheets in Project Server 2013
- Cannot open database after doing a "Reset Plan" on BeMo Content Pack
- Queue job Reporting Project Publish failed
- What are the Issues Fixed by Service Pack 2 (SP2) in Office and SharePoint 2010
- How to fix issue with a user trying to Login into the Project Pro using Terminal Service?