none
Hiding Tasks on TImesheets Until Start Date RRS feed

  • Question

  • Using Project Server 2010.    One of my PM's asked if there is a way to not have a task show up in a timesheet until the actual start date.       My thoughts are even if I set the definition of the Near Future Planning Wondow to "1" - the task will appear seven days prior to the start date.    The other option (obviously) is to have the PM's not add the tasks until the start date.  

    Do other options exist that would suppress tasks on resources timesheets until the actual start date? 

    Thank you!

    ~Randy Knight

    Tuesday, October 28, 2014 2:42 PM

Answers

  • Another option could be to set Publish task to "No" until actual start date.

    http://office.microsoft.com/en-001/project-help/publish-task-field-HA010167476.aspx


    kashif

    Tuesday, October 28, 2014 4:46 PM

All replies

  • Hi Randy,

    Indeed you have to set at least 1 week or greater for the near future planning window, 0 is not a possible value. The other way would be to configure that the timesheet are not auto populated but then it will be applicable for all users.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, MCP |

    Tuesday, October 28, 2014 3:31 PM
    Moderator
  • Another option could be to set Publish task to "No" until actual start date.

    http://office.microsoft.com/en-001/project-help/publish-task-field-HA010167476.aspx


    kashif

    Tuesday, October 28, 2014 4:46 PM
  • Thank you Kashif.....   for the life of me, I don't know why I didn't think about that idea!    :-)      I'll need to test this to see if it will actually "Remove" a task that is already on a resource's timesheet.     Cheers!

    Tuesday, October 28, 2014 5:54 PM
  • Hi Randy,

    Setting the task to publish "NO" will also remove it from any reporting process.

    I'd rather suggest to set the booking type to proposed.

    See this excellent article from MPUG about this topic.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    Tuesday, October 28, 2014 6:08 PM
    Moderator
  • Hi Randy, 

    Guillaume's suggestion would work as well.  Though thinking about best practices, it suggests to use close tasks to updates instead.

    http://technet.microsoft.com/en-us/library/hh694531(v=office.14).aspx


    kashif

    Tuesday, October 28, 2014 6:39 PM
  • Indeed the "close tasks to update" would also work, with the limitation that it will not be applied on existing timesheets.

    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    Tuesday, October 28, 2014 6:49 PM
    Moderator