Timesheet Classifications and Administrative Time

[Pras Ad]

We are trying to implement the Timesheets in PS 2007 environment. We have several standard non-project categories like Ticket Support, Workshops, Training etc.,

I am trying to understand the difference between using Administrative time categories for this and the Timesheet classifcations (and allowing users to submit unverifieid lines) for this non-project time! Need help in figuring out which option is better for these non-project time.

EggHeadCafe - Software Developer Portal of Choice
FLASH! ECMA CERTIFIES C# and THE CLI !!!
http://www.eggheadcafe.com/tutorial...ac73-5e3980697175/flash-ecma-certifies-c.aspx

 

[Dale Howard [MVP]]

Pras --

If it were me, I would set up Administrative time categories for Ticket
Support, Workshops, Training, etc. I would try to keep these to the
absolute MINIMUM, however, as they will appear on EVERY timesheet. And then
if users spend time on something that simply does not fit into ANY category,
I would have them use the Add Lines feature. However, stress to them to use
the standard Administrative time categories whenever possible. Hope this
helps.




in message news:[email protected]...

 

[Pras Ad]

Thank you Dale very much for the reply. Is there any specific reason why it is better to call these activities under admin time, rather than create new Timesheet Classifications? Is it just for consistency or would this affect any reporting down the lane?



Dale Howard [MVP] wrote:

Pras --If it were me, I would set up Administrative time categories for
16-Oct-09

Pras -

If it were me, I would set up Administrative time categories for Ticke
Support, Workshops, Training, etc. I would try to keep these to th
absolute MINIMUM, however, as they will appear on EVERY timesheet. And the
if users spend time on something that simply does not fit into ANY category
I would have them use the Add Lines feature. However, stress to them to us
the standard Administrative time categories whenever possible. Hope thi
helps

-
Dale A. Howard [MVP
VP of Educational Service
msProjectExpert
http://www.msprojectexperts.co
http://www.projectserverexperts.co
"We write the books on Project Server"

Previous Posts In This Thread:

EggHeadCafe - Software Developer Portal of Choice
USING TABLE TYPE TO ELIMINATE CURSORS
http://www.eggheadcafe.com/tutorial...c-7622a8091034/using-table-type-to-elimi.aspx

 

[Dale Howard [MVP]]

Pras --

Yes, for consistency of reporting in Data Analysis views and data extracted
from the Reporting database. This is assuming, of course, that you actually
want to report on the Timesheet data. If not, go with your original plan
using the Add Timesheet Lines feature. Hope this helps.




in message news:[email protected]...

 

[think0rdie]

Regarding Administrative time categories, there is one inconvenient
thing I found during setting up PWA 2007 in my organization.

Let's assume that a PWA user created a timesheet for a certain period
and already input actual work hours for some project tasks and
Administrative time categories.
In addition, let's assume during the period of the timesheet,
considerable number of tasks are newly assigined to the user because
the user becomes a member of a new project.
Then the user might delete the timesheet and create it again in order
to make the newly assigned tasks automatically appear on the
timesheet.

If this case happens, the actual work hours of project tasks which the
user already input is still there on the timesheet, while that of
Administrative time categories is completely cleared. As a result, the
user has to input actual work hours of Administrative time categories
again.

So, if you use Administrative time categories, you'd better let users
know if a timesheet is deleted, the actual hours of Administrative
time categories will be cleared and have to be input again.

If this trivial annoying thing is corrected by SP2, please ignore my
comment.

Regards,