Non-billable activities/tasks in TimeSheet?

[Dale Howard [MVP]]

Leon --

Well, now I am totally out of ideas. Perhaps someone else has a fresh idea
for you. Sorry I can't be more help.

 

[Leon Milbeck]

Here is an interesting observation.
In MSO Project 2007 - Task Information (when I double click a task that I
create)
The task's "Resource Name" = DEV (for the Team that I created)
The "Assignment Owner" = administrator

If I try to select DEV from the "Assignment Owner" pull-down I cannot

Why would that be?
In fact any new task that I enter now the "Assignment Owner" = administrator.

administrator is not a part of any team. Just a global user I use to access
PWA.

Thoughts?

Leon Milbeck
Eagerly awaiting books that I purchased form your sire (Thanks to Tim
Clark)

 

[Dale Howard [MVP]]

Leon --

OK, let's back up a few steps. The Assignment Owner for Team resources
defaults to the name of the person who publishes the project initially, and
you cannot change this. But this is not the cause of your problem, so
forget about this.

In the Resource Center in PWA, select one of your human resources and then
click the Edit Details button. On the Edit Resource page, check the Default
Assignment Owner for your human resource. The Default Assignment Owner for
the human should be his/her own name. Is this the case? If not, you need
to edit all of your human resources in the Resource Center and specify each
resource as his/her own Default Assignment Owner. Let us know what you
find.

 

[Leon Milbeck]

Default Assignment Owner was blank for all users ...
Changing now ... anything I need to do now to refresh the project so that
the Team feature works?

Thanks
Leon Milbeck

 

[Leon Milbeck]

When I login as administrator those tasks assigned to the DEV team show up as
tasks assigned to him. That is why I feel there is an issue with "Assignment
Owner" ...

Leon Milbeck

 

[Dale Howard [MVP]]

Leon --

Believe me, the problem with the Team resource is not the Assignment Owner
designation. Because you failed to specify a Default Assignment Owner value
for every human resource in your Enterprise Resource Pool, that is probably
the source of your problem. If you have assigned human resources to any
tasks in any project, you will have to apply the Task Update view, insert
the Assignment Owner column, and specify each human resource as his/her own
Assignment Owner in the project, and then republish the project. You will
only need to do this on existing projects. On future projects, the system
will set the Assignment Owner value as the one specified as the Default
Assignment Owner. Have you tried republishing the project to see if it
works now? Let us know.

 

[Dale Howard [MVP]]

Leon --

Try this:

1. Open the project in question.
2. Remove the DEV team resource from all assigned tasks.
3. Publish the project.
4. Assign the DEV team resource to tasks again.
5. Publish the project.

Does that help? Let us know.

 

[Leon Milbeck]

Really cannot say why this happened. All other resources had the correct
values.
Only the ones that I had assigned to the DEV team lost them.
I have fixed all values and re-tried.
Once again, the administrator can see these tasks while the DEV team cannot.
Only when a DEV team member goes in and Self-Assigns the task is when they
see it in PWA.

Scenario:
I have gone and created a brand new project with four teams.
I have have created only 4 tasks and assigned the Team (DEV, SQA, MGMT, CS)
to each one.
Save and Publish
Login as administrator and I now have 4 tasks assigned to me.
Login as any Team member and I see no tasks.
If I self-assign, then I see that specific team member's task.

Leon Milbeck

 

[Leon Milbeck]

I followed your steps and it did not work.

Leon Milbeck