diff options
| author | Lucas Lefèvre <lul@odoo.com> | 2019-07-05 07:13:27 +0000 |
|---|---|---|
| committer | Yannick Tivisse <yti@odoo.com> | 2019-07-17 07:33:11 +0000 |
| commit | 0954ead4a6a395639a327a9c042de21dd53a3e96 (patch) | |
| tree | 5be9107cf0851abbada4bf8581a084cc7cc96bd8 /addons/mass_mailing/models/mail_thread.py | |
| parent | 1b3db79273fec655c13c94d92d6f49c213c2a630 (diff) | |
[FIX] hr_attendance: Allow Marc Demo to checkout
As Marc Demo, at the begining of the month, through
the client action, you can checkin but not checkout.
There is one limitation in the way the attendance state is computed:
It uses the attendance with the most recent checkin date.
Therefore, if an attendance is created in the future, it's the later
attendance which is taken into account, not the current attendance.
Steps to reproduce the problem:
1. Create an attendance in the future with both start and end
date set.
2. Through the client action: checkin
=> the client action stays on the checkin screen because you are
considered as checkout. Hence you cannot checkout.
It's difficult to change the way the state is computed, especially
having the right triggers.
Adding a constraint to avoid attendance in the future is probably a
bad idea. It could unintentionaly fail if the user's time is off by
a few minutes on his computer.
On the other hand, this situation should rarely happen (only when manually
creating an attendance, which has little functional sense).
Solution: Fix demo data to avoid attendances in the future.
Tests needed to be adapted because they used demo data. They no longer
use demo data.
Diffstat (limited to 'addons/mass_mailing/models/mail_thread.py')
0 files changed, 0 insertions, 0 deletions
