Assignment group Field in Project / Project Task form in PPM

[Anusha_Rao]

Hi All,

This query is regarding the Assignment Group field of Project / Project task form.

In our requirements, PPM groups are different from ITSM groups.

Step1: As part of PPM, we identify the resource groups that should be working on Projects and Project Tasks and we create those groups from

Resource > Resources > Groups ( So these groups will contain pps_resource Role)

Step2: When Resource Manager create Resource Plan , Groups field will display these Group names and Resource Plan is created

Queries:

1. On the Project / Project task form, Assignment Group field is to assign it to a particular group so here also only the groups created at Step1 should be displayed right? Ideally the resource groups who are part of Resource Plan should be working on these projects right?

2. Our customer uses both ServiceNow ITSM and PPM and hence the groups of ITSM are also displayed in Assignment Group search field on Project / Project task form.

Please let me know how can I fix this issue since the ITSM groups who work on Incidents/Change Requests/Problems are different from the groups who work on Project Tasks?

Thanks,

Anusha

[Talya]

Hi All,

Please correct me if I am wrong:

Ideally the Assigned To field on Project/Project task form should show the users who have pps_resource role as they are the ones who will be working on Demand/Project right?

OOTB It doesn't show all the users who has pps_resource role, but only few of the users are displayed.

'Assigned to' field is extended from Task table and there is Overriden Reference criteria mentioned as below:

javascript:var util = new ProjectManagementUtils(); util.assignedToRefQual(current, SNC.PPMConfig.getProjectRole('user',current.getTableName()),true);

Can anyone please help me explaining this?

Thanks,

Talya

[Jon Miller1]

IMO, ServiceNow don't make this really clear in any documentation I've seen. The assign-to and assign group on a project task are not who will do the work. This is a big mind-set change if you're used to using MS-Project. The assignee of a project task in ServiceNow is who will update/close the task, typically the project manager. In the vast majority of the projects I manage, all of the tasks are assigned to me.

The reason I say this is the only people you can assign tasks to must have the project_user or project_manager role. That is, anybody assigned a project task consumes a SPM license.

The way I think ServiceNow expects you to manage this (again, I've not found any documentation to validate this) is to assign other task types for the actual work. Examples; enhancements, service requests, change requests, etc. This actually simplifies the project management process as you can, for example, have a single project task "Perform software development" with multiple enhancements associated with it. Similarly, if your project requires 10 server builds, there can be a single project task "Build servers" with 10 server build service requests associated with it.

Hope that makes sense.

Jon

[stevesmith]

OOTB there is a preference on the project record to "Derive assignee list from resource plan."  This will constrain the available pool of assignees by those with valid resource plans on the project. It will also require the assignee to have the it_project_user role to be assigned the task.

[Captain Gaming]

Hi @stevesmith @Anusha_Rao @Jon Miller1 @Talya 
In my situation derived assignee list from resource plan is true by default then can anyone explain working functionality of additional assignee list in project task?.
2.Field: derived assignee list from resource plan is false then what is the working functionality of additional assignee list in project task?