S
Suz
We have encountered a small problem at a client site and I was wondering if
any of you had come across the same situation:
We created a number of administrative projects for the various teams in the
IT group. We created all these projects on the server prior to migrating to
the new environment. On the day of the migration, June 5, we published
assignments to the various team members for these administrative projects. On
June 5th, we asked the team members to put in their time on these activities
retroactively to June 1st (our cutoff before going to prod was May 31st).
The problem is this: if the first timesheet entry made by a team member
against an administrative task is on the current date, everything is fine.
But if the first timesheet entry made to an admin task is for a date prior to
the current date, the system places an exclamation mark on the task in Web
Access, indicating that "...this task should have been completed on <date>
but is not yet completed.". This confuses the heck out of everyone, since
these tasks are not supposed to have any planned values.
If the first entry made against one of these tasks is on or after the
current date, then the individuals can later add additional entries for
previous dates without getting any messages or icons in PWA. But if the first
timesheet entry made against an administrative task is prior to the current
date, then the message appears and does not go away.
Have any of you encountered this situation before, and if so, do you know of
any solution to circumvent this problem?
Any help would be appreciated!
any of you had come across the same situation:
We created a number of administrative projects for the various teams in the
IT group. We created all these projects on the server prior to migrating to
the new environment. On the day of the migration, June 5, we published
assignments to the various team members for these administrative projects. On
June 5th, we asked the team members to put in their time on these activities
retroactively to June 1st (our cutoff before going to prod was May 31st).
The problem is this: if the first timesheet entry made by a team member
against an administrative task is on the current date, everything is fine.
But if the first timesheet entry made to an admin task is for a date prior to
the current date, the system places an exclamation mark on the task in Web
Access, indicating that "...this task should have been completed on <date>
but is not yet completed.". This confuses the heck out of everyone, since
these tasks are not supposed to have any planned values.
If the first entry made against one of these tasks is on or after the
current date, then the individuals can later add additional entries for
previous dates without getting any messages or icons in PWA. But if the first
timesheet entry made against an administrative task is prior to the current
date, then the message appears and does not go away.
Have any of you encountered this situation before, and if so, do you know of
any solution to circumvent this problem?
Any help would be appreciated!