A
Astro Boy
We have a number of generic resources in the resource pool, as you
would expect. These generics are part of the project team on nearly
every project in the tool, again as you would expect. These resources
are correctly marked as "Generic" in the resource pool. Everything
should be fine, right?
Two of the generics are showing up in Timesheet Summary in PWA, which
is strange because generics don't get timesheets. But wait, it gets
weirder.
Both generics are "assigned" (as much as generics are assigned) to
many many tasks across many many projects. However, each of the
generics is showing in Timesheet Summary with one task in one project
(not the same task and project for both generics, though).
But wait, it gets weirder yet.
In one case, the generic is assigned to the task in question. In the
second case, the generic is NOT assigned to the task in question.
I have never seen anything remotely like this. Any thoughts?
Please let me know if you need additional info.
TIA
would expect. These generics are part of the project team on nearly
every project in the tool, again as you would expect. These resources
are correctly marked as "Generic" in the resource pool. Everything
should be fine, right?
Two of the generics are showing up in Timesheet Summary in PWA, which
is strange because generics don't get timesheets. But wait, it gets
weirder.
Both generics are "assigned" (as much as generics are assigned) to
many many tasks across many many projects. However, each of the
generics is showing in Timesheet Summary with one task in one project
(not the same task and project for both generics, though).
But wait, it gets weirder yet.
In one case, the generic is assigned to the task in question. In the
second case, the generic is NOT assigned to the task in question.
I have never seen anything remotely like this. Any thoughts?
Please let me know if you need additional info.
TIA