Timesheet view - removing extraneous rows & columns

A

AndrewP

MS-Project 2007, Project Web Access:

I understand from another posting, and from trying things out myself,
that the 2007 "My timesheet" view is very inflexible. I would like to
do the following, mainly to save screen space and make it easier for
my users:

1. Remove the "planned" rows - they just take up screen space, and we
would rather people thought about what they had actually done than
take the easy route of pretending they have done what was planned.

2. (Configurably) remove the "Billing Category" column, as we use
"standard" all the time.

3. (Configurably) remove the "comment" column - we don't use it. I
prefer to get people to talk to each other, and at present we are all
co-located.

4. (Configurably) remove the "approval status" column.

If you know how to configure the above, then great - please let me
know.
If you work for a software house, then I suggest that there could be a
market for add-ons to do the above. It's probably not worth our while
to pay for one-off development, but we could find a budget for some
(reasonably priced) add-ons. If they were from a reputable
organisation then "shrink-wrapped", but if from an independent
software developer, we would be interested, but would probably need
source code as assurance.

Thanks & regards.
 
A

AndrewP

Thanks for the tip, Gary. However, I'm surprised you say this is a
first stab at a timesheet application - in my previous organisation I
implemented MS-Project Enterprise 2003 timesheets, which ran
moderately well, and were better than 2007 in some respects. I'm
quite happy with many of the aspects of Project timesheets - would
just like a few tweaks as per my original mail.

Anyway, thanks again for your time.

Best regards,
Andrew
 
P

Pawel

Hi AndrewP,

I run across the same idiosyncrasy of the PS2007 timesheet and made a simple
change in the CSS stylesheet used by the timesheet web page, that solves the
first (and IMHO the most important) problem: hides the "planned" rows.

All you need to do is to edit the pwastyle.css file on the server (in my
case it is located here:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\TEMPLATE\LAYOUTS\PWA\STYLES\pwastyle.css")

and add following line at the very end:
.XmlGridPlannedWork {display: none;}

Save the file and you are done.
You may need to force refresh of the timesheet page (pressing F5 in your
browser) to make that change visible to IE.

If you ever wanted to revert the change - just edit the file again and
remove the line.

Please note that this primitive solution disables showing of the "planned"
lines to everyone - users cannot select whether they want the lines to be
seen or not (as it happens with e.g. non-billable time lines).

But for my organization it workes great :)

Hope that helps,

Pawel
 
A

AndrewP

HiAndrewP,

I run across the same idiosyncrasy of the PS2007 timesheet and made a simple
change in the CSS stylesheet used by the timesheet web page, that solves the
first (and IMHO the most important) problem: hides the "planned" rows.

All you need to do is to edit the pwastyle.css file on the server (in my
case it is located here:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\TEMPLATE\LAYOUTS\PWA\STYLES\pwastyle.css")

and add following line at the very end:
.XmlGridPlannedWork {display: none;}

Save the file and you are done.
You may need to force refresh of the timesheet page (pressing F5 in your
browser) to make that change visible to IE.

If you ever wanted to revert the change - just edit the file again and
remove the line.

Please note that this primitive solution disables showing of the "planned"
lines to everyone - users cannot select whether they want the lines to be
seen or not (as it happens with e.g. non-billable time lines).

But for my organization it workes great :)

Hope that helps,

Pawel












- Show quoted text -
Click to expand...

Great - I can recommend Pawel's fix to anybody as a brilliantly simple
solution, provided you're happy for it to apply to all users of the
server. Personally, I can't think of a good reason to ever show the
"planned" line if you want the truth about what people have been
doing. It would only be useful if it were simple (7 hours a day on
one task all week), and if it were that simple then it would only take
seconds to fill it in manually.

Now if only someone could tell me how to get daily totals at the foot
of the timesheet, then my happiness would be complete (what a sad life
I have).
 
G

Gary L. Chefetz [MVP]

Adrew:

For some people, showing planned work is simply a way to let them see what
they're supposed to be working on and what percentage of effort they should
give it. I disagree that this encourages reporting dishonesty. Hostile
corporate cultures breed deceit, not software tools.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
G

GirlGeek

Adrew:

For some people, showing planned work is simply a way to let them see what
they're supposed to be working on and what percentage of effort they should
give it. I disagree that this encourages reporting dishonesty. Hostile
corporate cultures breed deceit, not software tools.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com








- Show quoted text -
Click to expand...

Well said, Gary! How'd you get so smart - :)
 
A

AndrewP

Adrew:

For some people, showing planned work is simply a way to let them see what
they're supposed to be working on and what percentage of effort they should
give it. I disagree that this encourages reporting dishonesty. Hostile
corporate cultures breed deceit, not software tools.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com








- Show quoted text -
Click to expand...

Yes, giving the "a priori" view is a good reason. Point taken.
 
Top