Daily updates from Odoo
Navigate
Branch
Friday, May 8, 2020
14 changes
New functionality added to Odoo
Adds a new accounting report to help companies monitor currency exposure and estimate gains or losses from exchange rate changes. Accountants can choose rates, review impacted accounts, exclude accounts when needed, and create automatic adjustment entries that reverse on a selected date.
Original PR description
on behalf of @william-andre
Enhancements to existing features
Customer rating settings and navigation were renamed and reorganized to make feedback tools clearer for users. The update also improves rating email behavior, dashboard access, website links, and keeps older customer rating links working so previously sent emails remain usable.
Original PR description
- Rename the 'Use Rating on Project' feature into 'Customer Ratings' - Rename the 'Set Email Template to Stages' link to 'Set a Rating Email Template on Stages' - Add an optional list view for the Stages menu - display warning if the rating_template_id field is set and if one of the selected project_ids doesn't have the rating_status field set to true - Project form view revamp - rename the '% on tasks' stat button into 'Customer Satisfaction' - Remove the 'no option' for the rating frequency field because it is required - project form : Add a 'Go to Website' stat button - Project dashboard: remove the 'Customer Ratings' menu item in more - Ratings page: the 'Last 30 days' filter include ratings from today - remove the Appointment / Helpdesk Customer Satisfaction / Live Support menu items TASK ID : 1251
The Sign app now offers a smoother signing flow, with better guidance between required fields and more accurate default signatures. Date fields are automatically filled using today's date in the user's preferred language format, reducing manual work and mistakes.
Original PR description
Improve user experience in the sign application. Task Id 2216067 Related odoo/odoo#48529
The Planning Gantt view now consistently shows an unassigned or undefined row at the top when users group schedules by roles, departments, projects, tasks, or employees. This makes it easier to spot work that has not been fully categorized or assigned, even when that group is currently empty.
Original PR description
It should be done for the following associations of group by:
['role_id']
['role_id', 'employee_id']
['role_id', 'department_id']
['department_id', 'role_id']
['project_id', 'department_id']
['project_id', 'employee_id']
['project_id', 'role_id']
['task_id', 'department_id']
['task_id', 'employee_id']
['task_id', 'role_id']Indian GST reports now use the updated GST treatment information instead of older removed fields. This helps keep tax reporting aligned with current data structures and improves the accuracy of report results, including reverse charge cases.
Original PR description
l10n_in_export_type and l10n_in_import_export field is removed and alternate data available in a new field l10n_in_gst_treatment So update related domain task: 2089217
Code cleanup and technical improvements
The way closed project stages are defined has been moved from the enterprise project area into the main Project app. This keeps related Helpdesk, Timesheets, and Field Service screens aligned with the central Project configuration and should make stage behavior more consistent.
Original PR description
Closed stage are moved to `project`. TaskID: 2205057
Miscellaneous changes
Task : https://www.odoo.com/web#id=2252432&action=327&model=project.task&view_type=form&cids=&menu_id=4720 Forward-Port-Of: odoo/enterprise#10464
Original PR description
Task : https://www.odoo.com/web#id=2252432&action=327&model=project.task&view_type=form&cids=&menu_id=4720 Forward-Port-Of: odoo/enterprise#10464
As of 5th of May 2020, Facebook has decided to deprecate a few endpoints: https://developers.facebook.com/docs/graph-api/changelog/2020-02-03-endpoint-deprecations We thought that those changes did not impact us because we don't directly use any of those endpoints. However, graphQL allows you to indirectly nest endpoint calls by accessing sub-fields on an endpoint definition. For example, if we ask for the following "fields" on the "comments" endpoints: 'likes.limit(0).summary(true)
Original PR description
As of 5th of May 2020, Facebook has decided to deprecate a few endpoints: https://developers.facebook.com/docs/graph-api/changelog/2020-02-03-endpoint-deprecations We thought that those changes did not impact us because we don't directly use any of those endpoints. However, graphQL allows you to indirectly nest endpoint calls by accessing sub-fields on an endpoint definition. For example, if we ask for the following "fields" on the "comments" endpoints: 'likes.limit(0).summary(true)' It will indirectly call the endpoint comments/likes, which is part of the deprecated ones. This was simply fixed by requesting the "like_count" field instead, which allows to keep the same behavior as before. (In other words, nothing changes functionally) Task 2191695 Forward-Port-Of: odoo/enterprise#10455
Courtesy of Federico Zanuttini (fza), Odoo Forward-Port-Of: odoo/enterprise#10456
Original PR description
Courtesy of Federico Zanuttini (fza), Odoo Forward-Port-Of: odoo/enterprise#10456
A user could see and edit all their shifts, including the non-published ones. TaskID: 2230201 Forward-Port-Of: odoo/enterprise#9650
Original PR description
A user could see and edit all their shifts, including the non-published ones. TaskID: 2230201 Forward-Port-Of: odoo/enterprise#9650
- Go to Helpdesk - Open a ticket - Activate Studio to edit the ticket form - Add a Many2many field related to "helpdesk.ticket" - Go to a ticket form and add another ticket in the newly added Many2many field - Save the ticket - Change the stage from the ticket form The following traceback is generated: ------------------------------------------------------------------------------------------ File "/home/odoo/src/enterprise/helpdesk/models/helpdesk_ticket.py", line 390, in name_get re
Original PR description
- Go to Helpdesk - Open a ticket - Activate Studio to edit the ticket form - Add a Many2many field related to "helpdesk.ticket" - Go to a ticket form and add another ticket in the newly added Many2many field - Save the ticket - Change the stage from the ticket form The following traceback is generated: ------------------------------------------------------------------------------------------ File "/home/odoo/src/enterprise/helpdesk/models/helpdesk_ticket.py", line 390, in name_get result.append((ticket.id, "%s (#%d)" % (ticket.name, ticket.id))) TypeError: %d format: a number is required, not NewId ------------------------------------------------------------------------------------------ opw-2244205 Forward-Port-Of: odoo/enterprise#10428
action_invoice_paid is the preferred hook when doing post-reconcile actions. Forward-Port-Of: odoo/enterprise#10399 Forward-Port-Of: odoo/enterprise#10377
Original PR description
action_invoice_paid is the preferred hook when doing post-reconcile actions. Forward-Port-Of: odoo/enterprise#10399 Forward-Port-Of: odoo/enterprise#10377
Steps to rperoduce the bug: - Let's consider a portal user PU - Create a subscription S for PU - Log with PU and go in your subscription on the portal - Filter by Closed Bug: A 403 error was raised because PU has no right to read sale.subscription.stage PS: We can add sudo in these two parts because a first check is made in function _prepare_portal_layout_values opw:2248630 Forward-Port-Of: odoo/enterprise#10414
Original PR description
Steps to rperoduce the bug: - Let's consider a portal user PU - Create a subscription S for PU - Log with PU and go in your subscription on the portal - Filter by Closed Bug: A 403 error was raised because PU has no right to read sale.subscription.stage PS: We can add sudo in these two parts because a first check is made in function _prepare_portal_layout_values opw:2248630 Forward-Port-Of: odoo/enterprise#10414
… traceback Steps to reproduce: - install payroll - go to payroll > work entries > work entries > list view > create - set a name > pick any employee > set a start date > select 'Compensatory Time Off' as a work entry type > set an end date Previous behavior: you get a traceback ValueError: Expected singleton: resource.calendar() Current behavior: period is calculated and set from start date and end date opw-2219429 Forward-Port-Of: odoo/enterprise#10105 Forward-Port-Of: odoo
Original PR description
… traceback Steps to reproduce: - install payroll - go to payroll > work entries > work entries > list view > create - set a name > pick any employee > set a start date > select 'Compensatory Time Off' as a work entry type > set an end date Previous behavior: you get a traceback ValueError: Expected singleton: resource.calendar() Current behavior: period is calculated and set from start date and end date opw-2219429 Forward-Port-Of: odoo/enterprise#10105 Forward-Port-Of: odoo/enterprise#9352