Daily updates from Odoo
Monday, December 9, 2019
10 changes · master
Resolved issues and error corrections
Users without timesheet permissions can now open project task views normally. This removes an access-related blocker so project work remains visible to the right users even when they do not use timesheets.
Original PR description
Current behavior before PR: If you have not at least the timesheet user right, you can't open project task as a field in not present in the view. Desired behavior after PR is merged: You can open the task view TaskId: 2148606 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix keeps attendee answer choices limited to the relevant event, reducing the chance of selecting incorrect information. It also improves event administration screens by making an email settings field use the full available width and by applying clearer default sorting for registrations and event type cards.
Original PR description
Add a domain that limits to the answers belonging an event only on the attendee form. Make the width of the event_type_mail_ids 100% Sort event.registrations by id DESC and Kanban view by name task-2071337 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix cleans up remaining outdated FontAwesome 5 styling in the Documents app that should have been removed earlier. It helps keep the interface consistent and avoids visual glitches from obsolete icon code.
Original PR description
This commit removes some code that wasn't properly reverted in b152a16b9b236d5d0645fe2f823ebe92257e7d2e
This change fixes how salary package simulation links are generated by removing a fragile filter setup. It helps HR teams create links more consistently and reduces the chance of errors during contract salary simulations.
Original PR description
FIXME: task id
This fix changes how eligible accounting reversal records are selected in the Helpdesk accounting flow. It replaces a fragile automatic filtering method with a more stable rule, reducing the chance of incorrect or missing choices for users.
Original PR description
Task 2115472
The contact map view now supports translations for its labels and buttons when users switch languages. This helps non-English users see the map interface consistently in their selected language, with only third-party zoom labels remaining untranslated.
Original PR description
steps to reproduce: -install contacts -go to settings>translations>languages and activate a second language, for example Ukrainian as it has been fully translated in 13.0 -switch to the Ukrainian language, go to contacts and open the map view you can see the fields are not translated they do not appear in the web_map.pot either translation seem to not happen because the templates.xml file was not living in the static/src folder the fields "Name" and "Address" are part of the contacts_enterprise module (so they will appear in contacts_enterprise.pot, not web_map.pot) the pot file of the contacts_enterprise module was not named properly previous behavior: most fields inside the map view and the buttons are not translatable current behavior: all text inside the map view is translatable except for the "zoom in/out" labels (they are part of a third party library) opw-2144401
This fixes an issue in the Helpdesk Sales Timesheet area related to calculated information and how it appears in the helpdesk view. It helps ensure users see accurate timesheet-related details when working with helpdesk records.
Original PR description
TaskID: 2148606
This fixes a display issue where an icon was not shown correctly in the IoT scan range interface. The change improves visual clarity for users working with IoT device scanning, with no expected impact on business processes.
Original PR description
Icon not corretly displayed
This fixes the Helpdesk sales order selection so it behaves correctly when no customer is set. Users can still access available sales orders instead of seeing an empty or blocked list, reducing friction when linking helpdesk tickets to sales information.
Original PR description
The existing (and likely immediately replaced) static domain would be *almost* correct, but did not take in account the partner_id condition of the dynamic one. To check: I'm guessing the static domain "doesn't work" in the case partner_id is unset because the ORM then warns/complains about the `(a child_of False)` expression. However we can just coalesce False to [], which is what expression.py also does (after warning about it). If we truly actually care about partner_id being unset, we can use the conditional section hack. Task 2115472
This fix removes an outdated filtering behavior in the rental setup wizard so users can access the expected product choices. It helps avoid confusion during rental configuration and supports smoother sales operations.
Original PR description
Task 2115472