Hello mra, I see this bug/issue has been fixed in the latest version of the server, although in my opinion this has not been fixed. Instead the problem has been shifted to another department. I see what user 'qdp' means when he thinks this is too much of a restriction, however, the actual signing in and out now needs to be done at the attendances tab. In this tab you can still sign in and out in the future, thus not solving the actual problem.
'qdp', can you think of any situation in which it is absolutely necesarry to make sign in and out actions in the future? Signing in and out in the past is a must-have in my opinion (because employees may forget to do so), and this seems to be the case now. A small suggestion would be to use the current server date and compare it to date supplied by the user. Furthermore, I personally don't think it is such a good idea to make the o2m field readonly, as is done now. This only spreads the functionality to more tabs. -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/676445 Title: Timesheet allows sign in in the future Status in OpenObject Addons Modules: Fix Released Bug description: When working in the timesheet module, the workflow does not allow you to "sign in" or "out" if you are working on a timesheet in the future. However, if you manually create attendance records in the future, you can assign them to the "sign in" and "sign out" actions just fine. This can then be confirmed without any trouble. Result is a situation where you can plan attendance on a day that has not even been here yet and confirm it as well. Working specs: - OpenERP 6.0 (rev 3017) - Ubuntu server 10.04 - Addons (rev 3929) _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
