I'd like to share our set up for dealing with non-project time...
We use a project similar to a PS2003 Administrative project to track
vacation, sick, non-project meetings, personal development, etc. In our
case, entry is done after the fact to capture non-project time. We do not
use the MyTimesheet functionality, since we can not have the same custom
fields attributed to them as we do for "regular" projects. This allows us to
get all the data on the same OLAP cube for data analysis. It also makes for
all entries to be done on the MyTask page; resources do not have to go
between the MyTask and MyTimesheet pages. For resource capacity forecasting,
I don't see why a resource couldn't enter time for the future when they know
they have vacation or training scheduled.
If this set up conflicts with any stardard best practices, please let me
know since I wouldn't want lead our company down the wrong path.
Thanks for the soapbox,
Brian