Some irritants (observations)

M

Mike

Proposals
- if you drill down into a proposal to see task details then hit
browser back icon, the proposal is left checked out.

Resource:
- Is the Inactive field (=No) in MSP the same as the Active field (=
Active) in PWA
- you can update the default assignment owner in MSP (Enterprise
resource pool) view but not the Timesheet Manager
- proposed assignments are displayed in my tasks views
- can't display assignment owner in pwa resource assignment view.

Finally a question:
On my task, page the Go to | Tasks Gantt Chart icon is greyed out.
This is working on another environment I have set up. Any thoughts
on why?

regards

Mike
 
D

Dale Howard [MVP]

Mike --

Thank you for your observations about Project Server 2007. I share similar
sentiments and yet I continue to forge ahead working on our company's two
books on Project Server 2007! :)

To respond to your observations, I would add these comments:

1. Proposals -- Yes, I noticed that behavior, which is why I try to use the
Close button on the page.

2. Inactive field vs. Active field -- Yes, they appear to convey the same
type of information, but in "opposite" ways. :)

3. Default Assignment Owner field and Timesheet Manager field -- When you
check out the Enterprise Resource Pool, the Default Assignment Owner field
is available in Project Professional 2007 but you cannot edit the data in
the field, as it is Read-Only. The Timesheet Manager field is not available
at all. Are you certain you can edit the Default Assignment Owner field in
Project Professional? I cannot.

4. Proposed assignments -- This is a documented bug in Project Server 2007.

5. Assignment Owner -- Yes, the Assignment Owner field is definitely
missing from the list of available fields in a Resource Assignments view in
PWA.

To answer your question, log into PWA with administrator permissions and
then click Server Settings - Task Settings and Display. Select the "Enable
ActiveX Gantt view for all users" option and click the Save button. Hope
this helps.
 
A

Astro Boy

Dale, you mention "documented bugs" - is MSFT publishing a bug list anywhere?
I sorta doubt it, but it never hurts to ask.

Some other P2007 irritants:

1. File>Exit from Project Pro does not always check your project back in,
and it can be difficult to see that it remains checked out. PWA>Server
Settings>Force Checkin Enterprise Objects does not show it checked out. Only
Project Pro>Tools>Local Project Cache>View Status>Errors will tell you it's
still checked out. To check it back in, you have to open the locally cached
version of the project, save it, and do File>Close.

2. Custom Field drop-down lists do not always display correctly in Project
Pro>Project>Project Information.
 
D

Dale Howard [MVP]

Astroy Boy --

For the latest list of bugs, refer to the following URL:

http://connect.microsoft.com/feedback/default.aspx?SiteID=235

You may or may not see my bugs there, as I report them through a private MVP
newsgroup in which several Microsoft Project team members have begun
participating on a regular basis.

1. I recommand the process of File - Close and then File - Exit, as with
the previous two versions of Project Server. I have noted that sometimes
the system checks in the project, but the Local Cache does not. I simply
delete it from the Local Cache and open it directly from the server. It is
a bug, for sure, but a little annoying one, like a gnat buzzing around your
head! :)

2. I have reported this cross-table pollution bug with custom enterprise
fields that have Lookup Tables. Even though the data looks wrong in the
pick list in Project Professional, it is correct in the database. It is a
display problem basically. I'm glad you have seen this, too.
 
A

Astro Boy

Zowie! Thanks for the link, Dale!

I have to disagree with you on the "buggishness" of the project check-in
thing. For those of us who know what's going on, it's an annoyance. However,
I'm deploying P2007 to a client-load of EPM newbies, and it's throwing them
into a tizzy of the highest order. Same thing with the Custom Field display
in Proj Pro. These sort of "user-facing" issues are significant when you're
trying to engender user acceptance and faith in the tool.

On the other hand, it's a new product and some bugs are part of the
expectation. If these are the biggest-impact problems we encounter, we should
hit our knees nightly, thanking the Almighty and Uncle Bill (not necessarily
in that order).
 
M

Mike

Mike --

Thank you for your observations about Project Server 2007. I share similar
sentiments and yet I continue to forge ahead working on our company's two
books on Project Server 2007! :)

To respond to your observations, I would add these comments:

1. Proposals -- Yes, I noticed that behavior, which is why I try to use the
Close button on the page.

2. Inactive field vs. Active field -- Yes, they appear to convey the same
type of information, but in "opposite" ways. :)

3. Default Assignment Owner field and Timesheet Manager field -- When you
check out the Enterprise Resource Pool, the Default Assignment Owner field
is available in Project Professional 2007 but you cannot edit the data in
the field, as it is Read-Only. The Timesheet Manager field is not available
at all. Are you certain you can edit the Default Assignment Owner field in
Project Professional? I cannot.

4. Proposed assignments -- This is a documented bug in Project Server 2007.

5. Assignment Owner -- Yes, the Assignment Owner field is definitely
missing from the list of available fields in a Resource Assignments view in
PWA.

To answer your question, log into PWA with administrator permissions and
then click Server Settings - Task Settings and Display. Select the "Enable
ActiveX Gantt view for all users" option and click the Save button. Hope
this helps.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultanthttp://www.msprojectexperts.comhttp://www.projectserverexperts.com
"We wrote the book on Project Server"








- Show quoted text -
Click to expand...

Dale

The activex setting did the trick.

You are right about the assignment owner field, it is read only. I
think I got excited about being able to display it, as opposed to the
timesheet manager field which you cannot.

regards

Mike
 
Top