-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16.0][ADD] hr_timesheet_overtime_rate_begin_end #33
base: 16.0
Are you sure you want to change the base?
Conversation
I think this correctly addresses the need in the internal task. Backporting this to v12 may be a touch tricky because v12 doesn't use compute for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just some changes depending on my other reviews in OCA/timesheet, otherwise lgtm.
hr_timesheet_overtime_begin_end/models/account_analytic_line.py
Outdated
Show resolved
Hide resolved
hr_timesheet_overtime_begin_end/models/account_analytic_line.py
Outdated
Show resolved
Hide resolved
008bef9
to
be05f31
Compare
be05f31
to
6f39f33
Compare
Temporarily rebased on top of #37 |
Ugh this is terrible. I wrote a test that fails: Problem: The rate is applied twice. Once on the transient record that is shown to the user before it is actually created, and then again when the transient record is written to the database. There are two solutions that I can see:
|
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
This functionality was completely unlinked from the rest of hr_timesheet_overtime. I would have done this in two commits, but then the files wouldn't move over cleanly, losing history. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
c09e734
to
7b15e21
Compare
…pi.model method This makes it easier to extend with additional available information on the record. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
6d5fbbd
to
8ead2d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the timesheet lines tree, the hours_worked
field appears before time_start
and time_stop
, while it would be more logical if it would appear after them, between time_stop
and unit_amount
.
No functional differences; code is a little prettier. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
By decreasing the priority, we make sure that hours_worked is as close to unit_amount as possible. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
234ea2e
to
b0b445e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just 1 small thing to fix, otherwise lgtm.
hr_timesheet_overtime_rate_begin_end/models/account_analytic_line.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
b0b445e
to
ace05fa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, approved too fast? some tests are still failing. is this because this still depends on other changes?
Description
Compatibility module, depends on OCA/timesheet#692
Built on top of #41
Odoo task (if applicable)
T12629
Checklist before approval