Can you assign multiple resources to a single task? (i.e. for ongoing weekly meeting)

[keithe]

We are looking at the differences between our current integrated Project Management and Resource Capacity planning system and noticed that in ServiceNow   that only one resource can be assigned to a task,   At this time in our current system we can make a task for an item, like a weekly meeting, to allow resources to charge there time for the duratio of the project.   Can this also be done in SN?

[arun_vydianatha]

We would recommend not to do that. We want people who have bought PPM (worker) licenses to be assigned to project tasks.

That is the reason why we have removed ITIL from assignee list. OOB Helsinki, ITIL do not have ACL read permissions on project tables.

[kellykaufmann]

To get back to the business need....is the need to just track time as a meeting (if so, they can just create a timecard to the category 'Meeting'), is the need to track general time to that Project (in which case, they can just create a timecard to the category "Project/Project Task", and for the Task in the time card select the PRJ)   that they are spending meeting time for that project, is the need to track time to that PRJ indicating it is a general meeting (in which case, they again would create a timecard to the category "Project/Project Task", and for the Task in the time card select the PRJ and I wonder if you can have a subcategory of 'Project meeting' created?) or do you want people to track time for a specific meeting task # for that project and you're asking about assignment so it populates their time card?  

[michaeljhiemstr]

Hi Kelly,

The business need is to reduce the load on our project managers so they don't have to make multiple tasks for the same project task which is inefficient. In some cases we may have a team of 10 or more on a single task. By using the additional assignee list they would only have to add names and not additional project tasks. They then have a time card auto created whenever they put an update on the single task. We currently are on Fuji in our production instance and are in the process of testing Helsinki in our dev environment. We create the additional tasks or time cards to capture effort and we consider a meeting for a project just task work. At this time the need to break out the time for meetings vs. task work is not justified. We try to keep things very simple as it is difficult at best to get engineers to even record their time let alone break it out into subcategories.  

[arun_vydianatha]

Starting Istanbul - time cards will be created for the user in Assigned to and Additional Assignee list automatically when they update the task (if the property Auto-create a users' time card when they update a task is set to Yes)

Starting istanbul - a change in behavior is it will create Time card only if user is in Assigned to or Additional Assignee list, any user who is not in the assignee list but coming and updating the task, for them time cards won't be created

[michaeljhiemstr]

Thanks for the additional information Arun!

Would this solve the issue I see where a timecard approver gets time card for any task they may have created even if it isn't assigned to them? I end up with about 100 time cards after I approve my staffs timecards for the previous week. Only thing I can think of was that I was the original creator of the project tasks.