Adding resource name to a work package in ms project

[mohanprasadgutta]

hello,

I am trying to add a new resource name to a ms project task.
but the newly added resource name is reflecting for all the mpp file.
If i want to make it appear only for that particular work package(task)
how can i achieve that?

Thanks in Advance.

Regards,
Mohan.

 

[Dave]

I'm not sure what you mean. As soon as the resource is 'in' the project
then there is the potential to assign them to any of the tasks. I don't
know of a mechanism by which a resource becomes automatically assigned
for all tasks.

The steps you should be following are:
- Add the resource to the project using the resource sheet view
(assuming you are not using a resource pool or Project Server)
- Select the task you want the resource to work on and assign them
(using the resource assignment dialogue or the task entry form for example).

 

[mohanprasadgutta]

Here is the senario.
There is one workpackage with name "user mgmt".
i opened the resource assignment dialog box and types a name "mohan" in
that which is not available in resource sheet.
I can assign the same resource name (mohan) for the other tasks by
selecting that resource name from the dropdown list.
But here my requirement is the resource name "mohan" which i have given
for workpackage "user mgmt" should not be available for other tasks in
the dropdown list of resource names.

thanks in advance.

Best Regards,
Mohan.

 

[Dave]

Here is the senario.
There is one workpackage with name "user mgmt".
i opened the resource assignment dialog box and types a name "mohan" in
that which is not available in resource sheet.
I can assign the same resource name (mohan) for the other tasks by
selecting that resource name from the dropdown list.
But here my requirement is the resource name "mohan" which i have given
for workpackage "user mgmt" should not be available for other tasks in
the dropdown list of resource names.

thanks in advance.

Best Regards,
Mohan.

I don't think you can do that and I can't see why you would want to.
Maybe I haven't understood correctly, but if you don't want to assign a
resource to a task then why is the option of not assigning them inadequate?

If every time a new task was added it was necessary to create
permissions for resources to determine who could work on it and who
couldn't, then managing the plan would become very onerous.

 

[mohanprasadgutta]

hello Trevor Rabey and Dave,
Thanks you for your valuable responses.
Actually i have to implement according to the requirements provided for
me.

@Trevor Rabey:your opinion
Are you concerned that you will double book (over-allocate) the
Resource?
That is fixed with leveling
Overallocating the resource is not my concern.
Resource list should be maintained for workpackages independently.
@Dave: your opinionIf every time a new task was added it was necessary
to create
permissions for resources to determine who could work on it and who
couldn't, then managing the plan would become very onerous.

Could you have any idea to implement it even though it becomes
burdensome.

thanks in advance.

Kind Regards,
Mohan

 

[Dave]

hello Trevor Rabey and Dave,
Thanks you for your valuable responses.
Actually i have to implement according to the requirements provided for
me.

@Trevor Rabey:your opinion
Are you concerned that you will double book (over-allocate) the
Resource?
That is fixed with leveling
Overallocating the resource is not my concern.
Resource list should be maintained for workpackages independently.
@Dave: your opinionIf every time a new task was added it was necessary
to create
permissions for resources to determine who could work on it and who
couldn't, then managing the plan would become very onerous.

Could you have any idea to implement it even though it becomes
burdensome.

thanks in advance.

Kind Regards,
Mohan

You can't do it with the native application. You would have to extend
it with VBA. This would mean writing an application that threw a
warning (or had some other behaviour you haven't specified) every time
that you tried to assign that resource to another task.

If you really want to go down this route and have a fixed resource pool
then I suppose you could device a dialogue which allows you to state
which resources can work on which tasks. Then if assignments are made
which contravene that, it would provide a warning.

The problem would be that it wouldn't be obvious from the standard
controls what the permissions were, so a user wouldn't know what
resources could/could not be assigned to a given task.

Can you provide greater insight as to why you need this?