This conversation has been merged. Please reference the main conversation: Hours accepted for a project task that the user is no longer a member of in Gen3 custom timesheet
The related issue (I think) is that if a task has an expiry date, the user can still enter data passed the expiry date. Although the system displays an error the user (for some reason) has not adjusted his timesheet. This has caused us issues on project totals as the hours are still included in the "live" data even though the timesheet is invalid. If the task is expired, can we force any entry past the expiry date to zero hours? We have encountered this issue with a number of our engineers who are quickly filling in their timesheet at the end of the day and miss the error displayed.
Also, if a task is CLOSED during the timesheet period, there is no error displayed and the user can still book time to it. This is a bigger issue I think.
In summary, as soon as a task is listed in a timesheet, there seems to be little control on what days the user can book time to it. OK an error message may or may not be displayed but it doesn't prevent a user from booking time to it and hence obscuring the "live" data. In the old gen2 standard timesheet template, the cells would be greyed out to prevent the user from booking time to it, which is how we expect the system to work. Now its proving to be problematic in that a user is confused on what days is available for booking his time to a particular task and when to look for another task as his PO budget has run out!! And these issues are being raised by our more senior engineers who know how the system should work.
There are no replies.