Tuesday, September 5, 2023
40 changes · master
Enhancements to existing features
The fleet vehicle search menu now presents the employee driver option more clearly as “Drivers (Employee)” and places it higher in the list. Search behavior has also been adjusted so users get more accurate driver-related vehicle results.
Original PR description
Before this commit, the 'Current Driver(Employee)' option was present within the search menu and appeared as the last choice in the search list. IMP: Following this commit, the 'Current Driver(Employee)' is renamed as 'Drivers(Employee)' and moved to the third position among the available search options and filter_domain is applied to get correct search results. taskId: 3459896
The task “Last Stage Update” date now refreshes whenever a task state changes, not only when it moves to a closing state. This date is also shown directly in the task list, helping teams see more easily when task progress was last updated.
Original PR description
This PR brings two small improvements related to the "Last Stage Update" task field: - Update the field when changing the task to any state, not just a closing state. - Display the field in the project.task list view, just before the state. Task-3455177
The Mail app now uses the label "To-Do" instead of "To Do" for activity types. This keeps wording consistent with the To-Do app and reduces small inconsistencies in the user experience.
Original PR description
upgrade: https://github.com/odoo/upgrade/pull/5057 Renaming the activity type 'To Do' into 'To-Do' so that the naming convention is consitent with the To-Do app. **task-3469745**
Odoo removed an outdated browser-detection dependency that was only needed for very old, unsupported browsers. This simplifies maintenance across website, portal, point of sale, project, manufacturing subcontracting, web editor, and slides areas without changing expected behavior for supported users.
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/46736 task-3439226 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Twitter wall feature no longer uses legacy browser compatibility checks for outdated browsers such as Internet Explorer. This simplifies maintenance while keeping the visual scaling behavior supported in modern browsers.
Original PR description
This commit aims at removing the need to rely on `$.browser`, which was mainly the case to support deprecated and unsupported browsers like MS Internet Explorer or old version of Firefox. Community PR: https://github.com/odoo/odoo/pull/133916 task-3439226
Updated demo data helps users see how project documents can be managed in realistic scenarios. It showcases turning off documents for a project, tagging files, and sharing selected files as download-only links for portal users.
Original PR description
This PR adds some demo data in documents to showcase the following features: - Disabling the "Documents" feature on a project. - Applying tags to documents. - Creating a share link by documents ids in download only (so that uploading is not available for that project in the portal). Task-2878833
This update renames a technical product setting so it does not conflict with the main Documents label introduced for product documents. It also adjusts where rental information appears on product pages so customers see it in the intended section.
Original PR description
new field `product_document_ids` on product.template will also use the label 'Documents'. Since the field project_template_use_documents is only a little technical UX field, it could use a less generic label. See also: * https://github.com/odoo/odoo/pull/132739 * https://github.com/odoo/upgrade/pull/5069
Appointment meeting links are now passed into calendar event details when Google Calendar is not synced. This helps attendees find the online meeting link directly from the appointment information, reducing confusion and missed meetings.
Original PR description
Propagate the discuss link to the location parameter when the calendar is not synced with google calendar. Task-3235765
Resolved issues and error corrections
This fix makes an automated test for single notifications run consistently instead of failing at random. It helps keep the bus messaging component's quality checks reliable, reducing false failures during development and release validation.
Original PR description
Before this commit, the "subscribe to single notification" test failed in an undeterministic fashion. This commit solves this issue. fixes runbot-24033
Code cleanup and technical improvements
This update streamlines styling across several HR-related apps by replacing custom design code with standard Bootstrap styling options. This should make the interface easier to maintain, more consistent, and potentially faster to load without changing core business workflows.
Original PR description
This PR is part of the SCSS reviewing process. The SCSS of the `hr` module is being changed to reduce the number of custom code lines. The goal is to use Bootstrap's SCSS variable to optimize the loading time and allow more flexibility. This PR affects the following modules : - hr_appraisal - hr_appraisal_skills - hr_contract_salary - hr_expense - hr_referral task-3244877 Requires : - https://github.com/odoo/enterprise/pull/38825 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Issue: ------ The `date` field of the `hr.attendance.overtime` model records is not the date of the related leave. Cause: ------ We use: `fields.Date.today()` instead of the leave field `date_from`. Solution: --------- Use `date_from` field of `leave`. opw-3433480 Forward-Port-Of: odoo/odoo#133607
Original PR description
Issue: ------ The `date` field of the `hr.attendance.overtime` model records is not the date of the related leave. Cause: ------ We use: `fields.Date.today()` instead of the leave field `date_from`. Solution: --------- Use `date_from` field of `leave`. opw-3433480 Forward-Port-Of: odoo/odoo#133607
When someone applies for a job that has no recruiter assigned, the applicant record will no longer automatically list the public website user as responsible. This keeps ownership fields accurate and avoids confusion for recruitment teams reviewing new applications.
Original PR description
Steps: - install hr_recruitment app - Create a job Positions without Recruiter - Published job Positions - Got To website and apply - Open applicant - Public user is set in applicant responsible Issue: public user is set if Recruiter is empty in job Position Fix: In this commit we have removed the default current user as the responsible applicant. task-3424017
This fixes a small usability issue in Odoo's web interface where search text stayed visible after selecting a record in avatar-style many-to-many tag fields. Users now get a cleaner input field after each selection, reducing confusion during data entry.
Original PR description
Before this commit, performing a search in a Many2manyTagsAvatarFields and selecting an element does not remove the search value from the input. Why not? The value passed to Autocomplete is the default ''. As this value never changes, onWillUpdateProps is never called and cannot empty the input. Solution: Use the resetOnSelect option to force the input to be reset at each select if props.value is the default value. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
List and kanban views now use the right display limits when users switch between grouped and ungrouped data. This prevents too many or too few groups or records from appearing, making navigation and reporting views more consistent.
Original PR description
Be in an ungrouped list or kanban view. The "limit" number of records is displayed (by default 80). Apply a group by. The same limit is applied for the number of groups, whereas there's a specific parameter ("groups_limit") for the number of groups to fetch and display. The same problem occurs the other way around (going from grouped to ungrouped), as in this case the groups_limit is kept when the view is no longer grouped.
This commit fixes the issue by forcing a reset of the limit when we go from grouped to ungrouped and from ungrouped to grouped.
We also add a test to ensure that the "groups_limit" is taken into account even when there're multiple groupbys, which wasn't the case in previous versions, but which is working as expected with the new model.
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe Knowledge share panel now immediately reflects changes when a user updates an article's workspace visibility. This avoids confusion from the selection snapping back and removes the need to reload the page to confirm the new setting.
Original PR description
Currently, the input selection controlling the visibility of the article in the workspace is not properly updated whenever the user selects a new value. The user has to reload the page to see the change. Steps to reproduce the error: 1. Create an article in "Workspace". 2. Open the share panel of the article you created. 3. Change the visibility of the article. => The input selection changes but returns to its initial state. TO BE: The input selection should be updated and reflect the new configuration of the article. task-3482257
This update streamlines styling across several HR apps by replacing custom code with standard Bootstrap styling where possible. It should make pages easier to maintain, improve loading flexibility, and fixes a few readability issues in referral and salary configurator screens.
Original PR description
This PR is part of the SCSS reviewing process. The SCSS of the hr module is being changed to reduce the number of custom code lines. The goal is to use Bootstrap's SCSS variable to optimize the loading time and allow more flexibility. This PR affects the hr module and its addons from the enterprise plan. Custom CSS that can be replaced by Bootstrap's SCSS classes has been refactored within this PR. This PR affects the following modules : - hr_appraisal - hr_appraisal_skills - hr_contract_salary - hr_expense - hr_referral task-3244877 Requires : - https://github.com/odoo/odoo/pull/116393
Before, when instatating the interfaces if there was an error inside Odoo could stop. This PR prevents that and simply avoids instantiating the interface which causes the error. Forward-Port-Of: odoo/odoo#133791
Original PR description
Before, when instatating the interfaces if there was an error inside Odoo could stop. This PR prevents that and simply avoids instantiating the interface which causes the error. Forward-Port-Of: odoo/odoo#133791
As the Activity button (clock icon) is the same kind of action it make sense to apply the text-muted on the quick assign. task-3382159 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#126226
Original PR description
As the Activity button (clock icon) is the same kind of action it make sense to apply the text-muted on the quick assign. task-3382159 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#126226
Commit 72a17bafba6e7 force the PO `date_order` to be >= at ` today() to ensure the select_seller method take the right seller price. This introduces an error in the MPS module that may need to create PO in the past. Instead, this commit patch the call to `_select_seller` to take at least `today()` opw: 3167094 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read t
Original PR description
Commit 72a17bafba6e7 force the PO `date_order` to be >= at ` today() to ensure the select_seller method take the right seller price. This introduces an error in the MPS module that may need to create PO in the past. Instead, this commit patch the call to `_select_seller` to take at least `today()` opw: 3167094 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134130 Forward-Port-Of: odoo/odoo#133759
As the use of Markup is enforced since [1], we must use a Markup string when adding the subject to incoming vendor bills body otherwise the chatter will contain the escaped html, making it quite difficult for users to understand it. opw-3453136 [1] https://github.com/odoo/odoo/pull/111850 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133206
Original PR description
As the use of Markup is enforced since [1], we must use a Markup string when adding the subject to incoming vendor bills body otherwise the chatter will contain the escaped html, making it quite difficult for users to understand it. opw-3453136 [1] https://github.com/odoo/odoo/pull/111850 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133206
Before this commit, when the browser was offline and when an attempt to make a `RTCPeerConnection` was made, a traceback was raised by firefox: > InvalidStateError: Can't create RTCPeerConnection when the network is down This commit prevents the creation of the `RTCPeerConnection` when the browser is offline. task-3186872 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133770
Original PR description
Before this commit, when the browser was offline and when an attempt to make a `RTCPeerConnection` was made, a traceback was raised by firefox: > InvalidStateError: Can't create RTCPeerConnection when the network is down This commit prevents the creation of the `RTCPeerConnection` when the browser is offline. task-3186872 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133770
…after_invoice_pdf_render If a web-service after the PDF generation failed but does a cr.commit(), the attachments should not be generated. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#132349
Original PR description
…after_invoice_pdf_render If a web-service after the PDF generation failed but does a cr.commit(), the attachments should not be generated. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#132349
Steps to reproduce the problem: - Go on the "Courses" application and select a course. - Edit. - Replace the main image of the course with one of your own. - Save. -> The function route `/web_editor/modify_image/` is called two times leading to the creation of two attachments instead of one. The `saveModifiedImages()` function iterates through editable elements and calls `/web_editor/modify_image/` for each image with a `o_modified_image_to_save` class inside those elements. In our cas
Original PR description
Steps to reproduce the problem: - Go on the "Courses" application and select a course. - Edit. - Replace the main image of the course with one of your own. - Save. -> The function route…
Steps to reproduce the problem: - Go on the "Courses" application and select a course. - Edit. - Replace the main image of the course with one of your own. - Save. -> The function route `/web_editor/modify_image/` is called two times leading to the creation of two attachments instead of one. The `saveModifiedImages()` function iterates through editable elements and calls `/web_editor/modify_image/` for each image with a `o_modified_image_to_save` class inside those elements. In our case, the image has an editable element parent that has itself an editable element parent. Because since [1], the `o_modified_image_to_save` class is removed after the `rpc` call, this class is not removed while the `saveModifiedImages()` loops on the second editable element parent of the image. As a result, `/web_editor/modify_image/` is called two times. Note that before [1], the process was partially wrong as well. `/web_editor/modify_image/` was indeed called only once but with the wrong arguments. This is now fixed by ensuring that the function is called with the arguments coming from the closest editable element. [1]: https://github.com/odoo/odoo/commit/8872aab2d108ff3e2ec06ca4579479898c87738c task-3451349 Forward-Port-Of: odoo/odoo#134061 Forward-Port-Of: odoo/odoo#130472
before this commit, on inheriting the function _get_custom_rendering_context_values the argument values are not received in the inherited function as it is not passed along with the super scenario: * consider that the payment link is shared to customer * customer made the full payment * once the sale or invoice is fully paid, the link has to be shown as fully paid or expired * for doing this, if we inherit the above function, the arguments is not passed to the function after this commi
Original PR description
before this commit, on inheriting the function _get_custom_rendering_context_values the argument values are not received in the inherited function as it is not passed along with the super scenario: * consider that the payment link is shared to customer * customer made the full payment * once the sale or invoice is fully paid, the link has to be shown as fully paid or expired * for doing this, if we inherit the above function, the arguments is not passed to the function after this commit, the argument values are passed to super and the value can be used re used in the further inherit of this function --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134088
=== ISSUE 1 === Prior to this commit, there was a missing padding on the `o_list_selection_box`. === ISSUE 2 === On mobile, Cog and Print icons had no margin and were stick next to their label. This commit fixes these issues. task-3454841 Part of task-3326263 BEFORE:  AFTER:  AFTER:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#130824
Steps to reproduce: 1. install l10n_ar_website_sale 2. try to checkout out using a guest account (without sigining in) 3. error on address form very similar to: https://github.com/odoo/odoo/pull/130455 Issue: due to https://github.com/odoo/odoo/pull/118701 public users can't read `l10n_ar.afip.responsibility.type` anymore Fix: open access to the models opw-3460719 Forward-Port-Of: odoo/odoo#133457
Original PR description
Steps to reproduce: 1. install l10n_ar_website_sale 2. try to checkout out using a guest account (without sigining in) 3. error on address form very similar to: https://github.com/odoo/odoo/pull/130455 Issue: due to https://github.com/odoo/odoo/pull/118701 public users can't read `l10n_ar.afip.responsibility.type` anymore Fix: open access to the models opw-3460719 Forward-Port-Of: odoo/odoo#133457
Current behaviour: --- When clicking on a note containing multi-line text, the textarea shrinks Expected behaviour: --- Note should show whole text Steps to reproduce: --- 1. Install sale_management 2. Head to Sales > Quotations 3. Click on any quotation line 4. Click on "Add a note" 5. Input multi-line text 6. Click on the "Save manually" button 7. Click again on the note 8. Note is only one character tall opw-3457234 --- I confirm I have signed the CLA and read the P
Original PR description
Current behaviour: --- When clicking on a note containing multi-line text, the textarea shrinks Expected behaviour: --- Note should show whole text Steps to reproduce: --- 1. Install sale_management 2. Head to Sales > Quotations 3. Click on any quotation line 4. Click on "Add a note" 5. Input multi-line text 6. Click on the "Save manually" button 7. Click again on the note 8. Note is only one character tall opw-3457234 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#132437
This traceback arises when a user tries to make a payment on the website. To reproduce this issue: 1) Install `website_sale` 2) open invoicing/configuration/journals 3) Change the journal type if it is `sales` for all journals 4) Install and enable `Wire Transfer` payment provider in `invocing/configuration/Payment Providers` 5) Now open `website/shop` add any product to `Cart` and proceed to checkout 6) Make a payment with `Wire Transfer` Error: ``` ValueError: Expected single
Original PR description
This traceback arises when a user tries to make a payment on the website. To reproduce this issue: 1) Install `website_sale` 2) open invoicing/configuration/journals 3) Change the journal type if it…
This traceback arises when a user tries to make a payment on the website.
To reproduce this issue:
1) Install `website_sale`
2) open invoicing/configuration/journals
3) Change the journal type if it is `sales` for all journals
4) Install and enable `Wire Transfer` payment provider in `invocing/configuration/Payment Providers`
5) Now open `website/shop` add any product to `Cart` and proceed to checkout
6) Make a payment with `Wire Transfer`
Error:
```
ValueError: Expected singleton: account.journal()
File "odoo/http.py", line 2134, in __call__
response = request._serve_db()
File "odoo/http.py", line 1710, in _serve_db
return service_model.retrying(self._serve_ir_http, self.env)
File "odoo/service/model.py", line 133, in retrying
result = func()
File "odoo/http.py", line 1737, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 1851, in dispatch
return self.request.registry['ir.http']._dispatch(endpoint)
File "addons/website/models/ir_http.py", line 233, in _dispatch
response = super()._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 191, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 717, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/payment_custom/controllers/main.py", line 17, in custom_process_transaction
request.env['payment.transaction'].sudo()._handle_notification_data('custom', post)
File "addons/payment/models/payment_transaction.py", line 669, in _handle_notification_data
tx._process_notification_data(notification_data)
File "addons/payment_custom/models/payment_transaction.py", line 71, in _process_notification_data
self._set_pending()
File "addons/sale/models/payment_transaction.py", line 53, in _set_pending
so.reference = tx._compute_sale_order_reference(so)
File "addons/sale/models/payment_transaction.py", line 27, in _compute_sale_order_reference
order_reference = invoice_journal._process_reference_for_sale_order(order_reference)
File "addons/account/models/account_journal.py", line 912, in _process_reference_for_sale_order
self.ensure_one()
File "odoo/models.py", line 5420, in ensure_one
raise ValueError("Expected singleton: %s" % self)
```
On `_compute_sale_order_reference` method, `invoice_journal` variable is getting values with the reference of `type=sale`.
See:-
https://github.com/odoo/odoo/blob/ebc4ed6c4fb11b01be28cf417b27de83d5361cef/addons/sale/models/payment_transaction.py#L20-L30
Because of user changed the type of journal, `invoice_journal` value will be empty recordset and it is referenced to call `_process_reference_for_sale_order` method.
In `_process_reference_for_sale_order` method `ensure_one()` is used, which leads to above traceback.
sentry-4392496618
Forward-Port-Of: odoo/odoo#131934Forward-Port-Of: odoo/odoo#130709
Original PR description
Forward-Port-Of: odoo/odoo#130709
Issue: ------ It is possible to modify the `recurring_invoice` field even if the product has already been sold. After closing the error message, it is possible to save the product with the modifications. Cause: ------ Even if we return an error message (>< raising an exception), the value is changed in the backend. opw-3483040 Forward-Port-Of: odoo/enterprise#46571
Original PR description
Issue: ------ It is possible to modify the `recurring_invoice` field even if the product has already been sold. After closing the error message, it is possible to save the product with the modifications. Cause: ------ Even if we return an error message (>< raising an exception), the value is changed in the backend. opw-3483040 Forward-Port-Of: odoo/enterprise#46571
Since odoo/odoo#128244, when in the workspace share popup 1. A user clicks on `Share` 2. `onClose` (via `saveRecord`) is called before our `onSave` handler 3. the flag `saved` is `false` and the share record is **deleted** 4. Bonus: the user gets a link thinks all is going fine, but of course it leads to nowhere. Note that onSavedRecords works anyway to solve this, so we can clean our class extension, but not completely as we're in stable. We take this opportunity to rename the c
Original PR description
Since odoo/odoo#128244, when in the workspace share popup 1. A user clicks on `Share` 2. `onClose` (via `saveRecord`) is called before our `onSave` handler 3. the flag `saved` is `false` and the share record is **deleted** 4. Bonus: the user gets a link thinks all is going fine, but of course it leads to nowhere. Note that onSavedRecords works anyway to solve this, so we can clean our class extension, but not completely as we're in stable. We take this opportunity to rename the cancel button into "Discard", so users can figure out that using the "Copy Link" button does not mean that the share will exist. I.e. if one clicks on "Copy link", then "Cancel" or "X", they also have a link to a deleted record. Task-3489334 Forward-Port-Of: odoo/enterprise#46813 Forward-Port-Of: odoo/enterprise#46690
Currently when you open the deferred expense or revenue report and there already exist deferral moves for that period, we show a banner indicating that. However the user has no direct way of going to the involved entries. This commit makes the message clickable to that a user can quicly access the mentioned entries. Also the message mentions the entries are posted, but they are not always. So we renamed the term to 'generated' instead. Furthermore an issue is fixed where you couldn't gener
Original PR description
Currently when you open the deferred expense or revenue report and there already exist deferral moves for that period, we show a banner indicating that. However the user has no direct way of going to the involved entries. This commit makes the message clickable to that a user can quicly access the mentioned entries. Also the message mentions the entries are posted, but they are not always. So we renamed the term to 'generated' instead. Furthermore an issue is fixed where you couldn't generate a grouped deferral entry when there already was an automatic one on the same date from before (when the mode was automatic). [task-3441804](https://www.odoo.com/web#id=3441804&menu_id=4720&cids=1&action=333&active_id=967&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#46798 Forward-Port-Of: odoo/enterprise#44940
This PR will allow people to generate a PDF containing a list of all attendees of an event. People can also manually select attendees and generate a PDF listing them. task-3470464 Forward-Port-Of: odoo/enterprise#46227
Original PR description
This PR will allow people to generate a PDF containing a list of all attendees of an event. People can also manually select attendees and generate a PDF listing them. task-3470464 Forward-Port-Of: odoo/enterprise#46227
The query for the pnd tax report in Thailand does not have a defined order. It may not always the same. Linked to runbot error 24566 Forward-Port-Of: odoo/enterprise#46792
Original PR description
The query for the pnd tax report in Thailand does not have a defined order. It may not always the same. Linked to runbot error 24566 Forward-Port-Of: odoo/enterprise#46792
Versions: --------- - 14.0e+ Steps to reproduce: ------------------- 1. install l10n_pe_edi; 2. switch company to PE Company; 3. create a new invoice in Accounting; 4. set operation type to "[1001] Operation Subject to Detraction"; 5. add a product with a price >= 700; 6. open the product screen; 7. set withhold code "Madera" & withhold percentage to 4.00, then save; 8. preview invoice. Issue: ------ The sentence in the middle of the page includes a percentage with the sign in
Original PR description
Versions: --------- - 14.0e+ Steps to reproduce: ------------------- 1. install l10n_pe_edi; 2. switch company to PE Company; 3. create a new invoice in Accounting; 4. set operation type to "[1001] Operation Subject to Detraction"; 5. add a product with a price >= 700; 6. open the product screen; 7. set withhold code "Madera" & withhold percentage to 4.00, then save; 8. preview invoice. Issue: ------ The sentence in the middle of the page includes a percentage with the sign in front of the number. Cause: ------ In the formatting string, `%%` is placed in front of `%s`. Solution: --------- Place the `%%` directly behind `%s`. opw-3478679 Forward-Port-Of: odoo/enterprise#46752
Bugfixes: - Balance Sheet line 'VI. Current profit (loss)': only the profit was taken from the P&L, not the loss, so the Balance Sheet was unbalanced when the P&L is a net loss. - Profit & Loss: Line 'Increase in inventories and work in progress' had the wrong sign. This is part of the task of re-balancing the Balance Sheets. I've verified that with these changes, the Balance Sheet is balanced regardless of the balances created in all the accounts. Affected versions: 16.0 -> master. t
Original PR description
Bugfixes: - Balance Sheet line 'VI. Current profit (loss)': only the profit was taken from the P&L, not the loss, so the Balance Sheet was unbalanced when the P&L is a net loss. - Profit & Loss: Line 'Increase in inventories and work in progress' had the wrong sign. This is part of the task of re-balancing the Balance Sheets. I've verified that with these changes, the Balance Sheet is balanced regardless of the balances created in all the accounts. Affected versions: 16.0 -> master. taskid:3239795 Forward-Port-Of: odoo/enterprise#46648
Purpose ======= Migrate social twitter to the new API. Changes ======= We can not search user by name anymore, we need to type their username directly. To know if we liked a tweet or not, we need to request a different endpoint `/2/users/:id/liked_tweets`, but we can not search on this endpoint, so we will need to iterate over ALL the tweets the users liked (each time we want to update the like status). So we do not synchronize the like status with Twitter (the like status is just stor
Original PR description
Purpose ======= Migrate social twitter to the new API. Changes ======= We can not search user by name anymore, we need to type their username directly. To know if we liked a tweet or not, we need to request a different endpoint `/2/users/:id/liked_tweets`, but we can not search on this endpoint, so we will need to iterate over ALL the tweets the users liked (each time we want to update the like status). So we do not synchronize the like status with Twitter (the like status is just stored in the database). See https://developer.twitter.com/en/docs/twitter-api/tweets/likes/introduction Task-3431873 Forward-Port-Of: odoo/enterprise#46782 Forward-Port-Of: odoo/enterprise#44625
Before this commit, `o-gantt-zindex` mixin was used for the styling in grid renderer component, the problem is that mixin is defined in `web_gantt` module and that module is not in the dependencies of `web_grid` module. This commit creates a new mixin function called `o-grid-zindex` to use it instead of `o-gantt-zindex` for grid renderer to be sure the mixin function is available even if web_gantt is not installed Forward-Port-Of: odoo/enterprise#46561
Original PR description
Before this commit, `o-gantt-zindex` mixin was used for the styling in grid renderer component, the problem is that mixin is defined in `web_gantt` module and that module is not in the dependencies of `web_grid` module. This commit creates a new mixin function called `o-grid-zindex` to use it instead of `o-gantt-zindex` for grid renderer to be sure the mixin function is available even if web_gantt is not installed Forward-Port-Of: odoo/enterprise#46561
The introduction of sections in reports put in light an inappropriate behavior in the dispatching of the option buttons. In a browser, when the currently displayed report is a section of another, the `dispatch_report_action` (`controller.js` in `account_reports`) would dynamically adapt the buttons to have them use the original report id. Hence, there would be no problem in the browser. However, during testing, `dispatch_report_action` can't do its magic ; a button is called from the secti
Original PR description
The introduction of sections in reports put in light an inappropriate behavior in the dispatching of the option buttons. In a browser, when the currently displayed report is a section of another, the `dispatch_report_action` (`controller.js` in `account_reports`) would dynamically adapt the buttons to have them use the original report id. Hence, there would be no problem in the browser. However, during testing, `dispatch_report_action` can't do its magic ; a button is called from the section instead of its parent, causing the test to fail. Adapted the test to take sections into account. Forward-Port-Of: odoo/enterprise#46817
Before this commit, when the currency of the order did not matched the current currency, the result were not properly displayed in the list view. Forward-Port-Of: odoo/enterprise#46323
Original PR description
Before this commit, when the currency of the order did not matched the current currency, the result were not properly displayed in the list view. Forward-Port-Of: odoo/enterprise#46323