-
Notifications
You must be signed in to change notification settings - Fork 41
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][MIG] shift attendance: migration to 16.0 #538
base: 16.0
Are you sure you want to change the base?
Conversation
3cc8164
to
292d8e3
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.
functional test on 16-test-shift
@remytms see bug reports below when clicking on today's attendance sheet submenu
features
- add attendance sheet configs, model, menu and submenus
- automated action - attendance sheet generation
- apply attendance sheet content to shift upon validation
- raise validation errors when the shift hasn't started
- add permission group to validate attendance sheets
- trigger email in case of missed shift NOK : default template content baldy rendered
bug report: can't access Attendance Sheet > "Today's sheets" submenu
Promesse non interceptée > fnValue is not a function
TypeError: fnValue is not a function
_innerEvaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1299:8
_evaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1306:49
_innerEvaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1295:33
_evaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1306:49
_innerEvaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1295:33
_evaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1306:49
evaluate@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1308:8
evaluateExpr@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:1155:109
_preprocessAction@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:5881:150
doAction@https://odoo16.main.test.srv.coopiteasy.be/web/assets/231-3bfc478/web.assets_backend.min.js:5966:170
```
@remytms
|
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
* rename many2many tables and their columns. * rename constraints and indexes.
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
There are two fixes in this commit: - Use .search() instead of .get_param() for a more robust search of the old value. - Rename all XMLIDs. When they XMLIDs aren't renamed, the values get overridden during init, even though the config_parameter keys were renamed. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
68687b2
to
e45e1ba
Compare
@remytms Still having similar issues, try previewing the email template here. |
@polchampion I also add some trouble with transalation in french that does not reflect the changes. I deleted the email template, and updated the module. Now the mail template, does not contain the typo "objec.xxx" that shows up in your previous error. I also face issue when choosing to preview with a shift with no worker assigned. I’m not sure that this case should be taken into account, knowing that the worker is needed also for the "To" field o the email. Can you test again ? |
Description
Odoo task (if applicable)
task
Checklist before approval