Hello,
i do not agree with you: i don't want to have something too restricted
because we often need to make manual sign in/sign out, and the buttons
are not permissive at all. I'd suggest to set the o2m field of
attendances on the timesheet_sheet as readonly, and let the option to do
something more flexible using the menu of attendances...
thanks
** Changed in: openobject-addons
Importance: Medium => Low
** Changed in: openobject-addons
Milestone: None => 6.0-rc2
--
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:
In Progress
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
