Daily updates from Odoo
Tuesday, November 7, 2023
51 changes · master
Enhancements to existing features
Chilean localization tax names, descriptions, and translations have been improved to make them clearer and more consistent. Related automated tests were updated so tax reporting and electronic invoicing checks continue to match the new wording.
Original PR description
CL now has improved tax names, so the test needs to be adjusted accordingly
Code cleanup and technical improvements
This update removes an outdated internal translation helper from parts of the codebase. It helps keep the platform easier to maintain without changing day-to-day user workflows.
Original PR description
In this commit, _lt is definitly removed from codebase. task-3292454
The WhatsApp module was updated to use a cleaner internal approach for handling date and time values. This reduces reliance on older formatting constants and helps keep the codebase easier to maintain without changing expected user behavior.
Original PR description
Enterprise counter-part. https://github.com/odoo/odoo/pull/141320
This update removes unused testing support code from the Facebook social media module. It does not change customer-facing behavior, but helps keep the codebase simpler and easier to maintain.
Original PR description
https://github.com/odoo/odoo/pull/141025
Miscellaneous changes
Steps to reproduce: - Activate "Analytic Accounting" in Accounting settings - Create an invoice with an analytic account (e.g. Administrative) - Archive the used analytic account (i.e. Administrative) - Go "Accounting / Reporting / Audit Reports / General Ledger" - Click on "Analytic" button - When selecting Accounts, click on "Search More..." - Filter "Archived" accounts - Select an archived account (e.g. Administrative) => The filter is selected but it is not taken into account. The
Original PR description
Steps to reproduce: - Activate "Analytic Accounting" in Accounting settings - Create an invoice with an analytic account (e.g. Administrative) - Archive the used analytic account (i.e. Administrative) - Go "Accounting / Reporting / Audit Reports / General Ledger" - Click on "Analytic" button - When selecting Accounts, click on "Search More..." - Filter "Archived" accounts - Select an archived account (e.g. Administrative) => The filter is selected but it is not taken into account. The displayed data stay unchanged. There is the same issue with partner filter in "Partner Ledger" report. opw-3514165 Forward-Port-Of: odoo/enterprise#50308 Forward-Port-Of: odoo/enterprise#49856
On some db without demo data and in particular configuration, the changes introduced in https://github.com/odoo/enterprise/pull/49333 create a problematic situation where no progress bar info is available for a row with an employee. This commit avoids such traceback by falling back on the relation used for employee_id field if no info is available in the progress bar on the model used. Forward-Port-Of: odoo/enterprise#50215 Forward-Port-Of: odoo/enterprise#50169
Original PR description
On some db without demo data and in particular configuration, the changes introduced in https://github.com/odoo/enterprise/pull/49333 create a problematic situation where no progress bar info is available for a row with an employee. This commit avoids such traceback by falling back on the relation used for employee_id field if no info is available in the progress bar on the model used. Forward-Port-Of: odoo/enterprise#50215 Forward-Port-Of: odoo/enterprise#50169
Step to reproduce: 1. Install appointment, website_appointment and appointment_account_payment 2. Go to the appointment module 3. Create a new resource type appointment 4. <img width="1583" alt="Screenshot 2023-11-03 at 14 42 41" src="https://github.com/odoo/enterprise/assets/15966645/4eea81ce-0201-4826-ba00-b434ef5f8347"> 5. Click on `Go to website` 6. <img width="1338" alt="Screenshot 2023-11-03 at 14 17 16" src="https://github.com/odoo/enterprise/assets/15966645/8e582cdd-fbd6-4f20-8000
Original PR description
Step to reproduce: 1. Install appointment, website_appointment and appointment_account_payment 2. Go to the appointment module 3. Create a new resource type appointment 4. <img width="1583" alt="Screenshot 2023-11-03 at 14 42 41" src="https://github.com/odoo/enterprise/assets/15966645/4eea81ce-0201-4826-ba00-b434ef5f8347"> 5. Click on `Go to website` 6. <img width="1338" alt="Screenshot 2023-11-03 at 14 17 16" src="https://github.com/odoo/enterprise/assets/15966645/8e582cdd-fbd6-4f20-8000-8aa2a39d73be"> For a resource type appointment, the staff_user does not exist. Forward-Port-Of: odoo/enterprise#50140
This commit address several UI issues: - Adjust base font-size on xxl screens - DrinkPage component: ensure that the footer is fixed and that the scrollbar is applied on the products grid. - DrinkPage component: introducing grid's column adaptations according to the number of products rendered on screen. task-3581651 Forward-Port-Of: odoo/enterprise#50128
Original PR description
This commit address several UI issues: - Adjust base font-size on xxl screens - DrinkPage component: ensure that the footer is fixed and that the scrollbar is applied on the products grid. - DrinkPage component: introducing grid's column adaptations according to the number of products rendered on screen. task-3581651 Forward-Port-Of: odoo/enterprise#50128
Fix the missing padding between the icon and the field label in the inspector. Task-3562216 Forward-Port-Of: odoo/enterprise#50089 Forward-Port-Of: odoo/enterprise#49401
Original PR description
Fix the missing padding between the icon and the field label in the inspector. Task-3562216 Forward-Port-Of: odoo/enterprise#50089 Forward-Port-Of: odoo/enterprise#49401
The default 'Unit' uom was always displayed on the shop floor for moves as the `displayUOM` was not checked within the `props`. Forward-Port-Of: odoo/enterprise#50005
Original PR description
The default 'Unit' uom was always displayed on the shop floor for moves as the `displayUOM` was not checked within the `props`. Forward-Port-Of: odoo/enterprise#50005
Steps to Reproduce =================== - Open appointment in which your are part of that. - Try to share the interview meeting. - Warning will be there even if a user is part of that meeting. Technical ========== Due to some typos here https://github.com/odoo/enterprise/commit/d1e75bf651ba06ce065afa8e6ca18e6b25e2dfce After this pr ================== There will be no warning if the user is a part of it. Task-3487715 Forward-Port-Of: odoo/enterprise#49607
Original PR description
Steps to Reproduce =================== - Open appointment in which your are part of that. - Try to share the interview meeting. - Warning will be there even if a user is part of that meeting. Technical ========== Due to some typos here https://github.com/odoo/enterprise/commit/d1e75bf651ba06ce065afa8e6ca18e6b25e2dfce After this pr ================== There will be no warning if the user is a part of it. Task-3487715 Forward-Port-Of: odoo/enterprise#49607
Problem --------- The "Notes" field in Bank Reconciliation list view (optional_hide) should be editable. It's not working anymore in 17, it's working in 16.4. Steps --------- 1. Install `account_accountant` 2. Accounting Dashboard > Bank journal > List view 3. Unhide Note column > Click on any empty notes Solution --------- The field was set as invisible when it was empty. However, this appeared to also hide the editable box from the HTML field. The box was then not clickable a
Original PR description
Problem --------- The "Notes" field in Bank Reconciliation list view (optional_hide) should be editable. It's not working anymore in 17, it's working in 16.4. Steps --------- 1. Install…
Problem --------- The "Notes" field in Bank Reconciliation list view (optional_hide) should be editable. It's not working anymore in 17, it's working in 16.4. Steps --------- 1. Install `account_accountant` 2. Accounting Dashboard > Bank journal > List view 3. Unhide Note column > Click on any empty notes Solution --------- The field was set as invisible when it was empty. However, this appeared to also hide the editable box from the HTML field. The box was then not clickable and thus not editable. Removing the invisible attribute solves the issue while maintaining the idea that nothing should be shown (no empty box) if there is no note content. From this fix, another issue appeared back in the Kanban view: the notes field was editable with a sequencing arrow appearing on the left. We don't want the note field to be editable in the Kanban view. To solve the issue, we replace the HtmlField tag in the XML template by a t-out so that the attribute set on the python fields are used in the view. task-3537776 Forward-Port-Of: odoo/enterprise#49383
The current demo city in PL payroll demo data is Vilnius. It would be nicer to change it to a Polish city., so this commit changes it to Krakow. Forward-Port-Of: odoo/enterprise#50323 Forward-Port-Of: odoo/enterprise#50285
Original PR description
The current demo city in PL payroll demo data is Vilnius. It would be nicer to change it to a Polish city., so this commit changes it to Krakow. Forward-Port-Of: odoo/enterprise#50323 Forward-Port-Of: odoo/enterprise#50285
Steps to reproduce: - Install the delivery_ups module - Log in as Marc Demo - Create a SO and set Mitchell Admin as Customer - Try to save or confirm the order The user will get an access rights error because he's not able to update `res.users` records. This commit makes sure the update done in the inverse of the `partner_ups_carrier_account` is done in sudo, not triggering unexpected access errors. task-3519499 Forward-Port-Of: odoo/enterprise#48093
Original PR description
Steps to reproduce: - Install the delivery_ups module - Log in as Marc Demo - Create a SO and set Mitchell Admin as Customer - Try to save or confirm the order The user will get an access rights error because he's not able to update `res.users` records. This commit makes sure the update done in the inverse of the `partner_ups_carrier_account` is done in sudo, not triggering unexpected access errors. task-3519499 Forward-Port-Of: odoo/enterprise#48093
When we make a reevaluation with an increase, the date where you make the increase has no impact. It's depreciated for the whole duration of the parent asset. It does not make sense, and should be from the moment where the asset is reevaluated. The child asset will have a lifetime depending on the time left for the parent. For degressive then linear, we try to follow the curve of the parent opw-3526524 Forward-Port-Of: odoo/enterprise#50204 Forward-Port-Of: odoo/enterprise#48629
Original PR description
When we make a reevaluation with an increase, the date where you make the increase has no impact. It's depreciated for the whole duration of the parent asset. It does not make sense, and should be from the moment where the asset is reevaluated. The child asset will have a lifetime depending on the time left for the parent. For degressive then linear, we try to follow the curve of the parent opw-3526524 Forward-Port-Of: odoo/enterprise#50204 Forward-Port-Of: odoo/enterprise#48629
Before this commit, when the user copies the shifts in the previous week and then auto plan, an error occurs because a record is used but it does no longer exist in the database. The reason is the shift unplanned will be used in the auto plan feature to plan it to an available resource but the problem is that shift has allocated_hours equals to 0 and so it is removed in the process since it means we have no longer something to plan for a specific SOL. This commit recomputes the `planning_hour
Original PR description
Before this commit, when the user copies the shifts in the previous week and then auto plan, an error occurs because a record is used but it does no longer exist in the database. The reason is the shift unplanned will be used in the auto plan feature to plan it to an available resource but the problem is that shift has allocated_hours equals to 0 and so it is removed in the process since it means we have no longer something to plan for a specific SOL. This commit recomputes the `planning_hours_planned` to be sure the post_process, called in the create method, remove the shifts unplanned with allocated hours equals to 0. Forward-Port-Of: odoo/enterprise#50275
Doing `''.join(Markup)` converts to string Forward-Port-Of: odoo/enterprise#50287
Original PR description
Doing `''.join(Markup)` converts to string Forward-Port-Of: odoo/enterprise#50287
Issue: ====== When we sign documents related to sale order , the signer id default value is the user and not the customer. Steps to reproduce the issue: ============================= - Install sign and rental - Activate Digital Documents in settings. - Create a sale order and confirm it and Click sign docuemnts - Click sign documents again - The customer value is mitchel admin and not the real customer. Solution: ========= I added default signer in the context of the action.
Original PR description
Issue: ====== When we sign documents related to sale order , the signer id default value is the user and not the customer. Steps to reproduce the issue: ============================= - Install sign and rental - Activate Digital Documents in settings. - Create a sale order and confirm it and Click sign docuemnts - Click sign documents again - The customer value is mitchel admin and not the real customer. Solution: ========= I added default signer in the context of the action. opw-3540712 Forward-Port-Of: odoo/enterprise#50272 Forward-Port-Of: odoo/enterprise#48994
Steps to reproduce: - From Accounting dashboard, view Operations of Bank journal (3-dots button) - Display Notes (narration) field - Create a new Bank statement line with a very long note and an amount - Click on "MATCH" button - On reconciliation widget, go to "Manual Operations" tab - Resize the browser window by reducing the width => Many labels will be displayed in an element with a very small width, appearing vertically. Like this: L a b e l opw-3524146 opw-3538692 Forwar
Original PR description
Steps to reproduce: - From Accounting dashboard, view Operations of Bank journal (3-dots button) - Display Notes (narration) field - Create a new Bank statement line with a very long note and an amount - Click on "MATCH" button - On reconciliation widget, go to "Manual Operations" tab - Resize the browser window by reducing the width => Many labels will be displayed in an element with a very small width, appearing vertically. Like this: L a b e l opw-3524146 opw-3538692 Forward-Port-Of: odoo/enterprise#50261 Forward-Port-Of: odoo/enterprise#49924
This commit fixes an issue introduced in Commit[1]. Prior to Commit[1], the `border-color` property of our input was overridden in Enterprise to a `$o-gray-200` value. Commit[1] aimed to fix an issue inside list view where the "add item" button would have a grey background on focus state, by setting the background to a light gray color. Unfortunately, this commit didn't take into account the fact that `$o-form-lightsecondary` is also handling the `border-color` of our input in the hover st
Original PR description
This commit fixes an issue introduced in Commit[1]. Prior to Commit[1], the `border-color` property of our input was overridden in Enterprise to a `$o-gray-200` value. Commit[1] aimed to fix an issue inside list view where the "add item" button would have a grey background on focus state, by setting the background to a light gray color. Unfortunately, this commit didn't take into account the fact that `$o-form-lightsecondary` is also handling the `border-color` of our input in the hover state. By changing it to `$o-gray-100`, it made it barely impossible to notice. This commit reverts that change, ensuring the `border-color` remains visible in every state. Commit[1]: https://github.com/odoo/enterprise/commit/74bc70a35897274d0bd8d8e53abbdbb48174d8f0 task-3575546 Forward-Port-Of: odoo/enterprise#49832
Community: https://github.com/odoo/odoo/pull/141127 Forward-Port-Of: odoo/enterprise#50247
Original PR description
Community: https://github.com/odoo/odoo/pull/141127 Forward-Port-Of: odoo/enterprise#50247
…ounting dashboard - burger menu cleanup 1. Remove some options from the burger menu to make it more clear. 2. Make some actions on the journal's dashboard card conditional on the Bank Feed type. task-id: 3573286 Forward-Port-Of: odoo/enterprise#49762
Original PR description
…ounting dashboard - burger menu cleanup 1. Remove some options from the burger menu to make it more clear. 2. Make some actions on the journal's dashboard card conditional on the Bank Feed type. task-id: 3573286 Forward-Port-Of: odoo/enterprise#49762
URL should avoid _ in them, so the url was changed Forward-Port-Of: odoo/enterprise#50267
Original PR description
URL should avoid _ in them, so the url was changed Forward-Port-Of: odoo/enterprise#50267
- added a check on rule creation in stock_warehouse to avoid duplicates of the push rule when switching between multisteps options this happens when modules which remove the initial pull rule (e.g. mrp, purchase_stock) are installed along with sale_stock_renting - removed _set_quantities_to_reservation because the parent function doesn't exist anymore. - removed write because it doesn't bring anything and a standard SO doesn't do that anyway - Changed text in the Configuration>Settings menu
Original PR description
- added a check on rule creation in stock_warehouse to avoid duplicates of the push rule when switching between multisteps options this happens when modules which remove the initial pull rule (e.g. mrp, purchase_stock) are installed along with sale_stock_renting - removed _set_quantities_to_reservation because the parent function doesn't exist anymore. - removed write because it doesn't bring anything and a standard SO doesn't do that anyway - Changed text in the Configuration>Settings menu to match rest of UI texts Forward-Port-Of: odoo/enterprise#50245
This commit fixes a bug where when a user would try to export an article the anchors for comments were still stylized. This led to printing documents with unnecessary noise in the article. Now, we added the media css query `@media screen` for comment anchors so that we apply the style when using a screen. Removing the style from the printed document. task-3572009 Forward-Port-Of: odoo/enterprise#49714
Original PR description
This commit fixes a bug where when a user would try to export an article the anchors for comments were still stylized. This led to printing documents with unnecessary noise in the article. Now, we added the media css query `@media screen` for comment anchors so that we apply the style when using a screen. Removing the style from the printed document. task-3572009 Forward-Port-Of: odoo/enterprise#49714
Before this commit, some tools of website_sale_renting were broken due to a loading problem of the overrides of the Variant mixin. For instance, the price on the product page was not depending on the rental period anymore. We now force them to be executed by prepending the js files in the manifest. Furthermore, the dates were not always given in the context. In this case, the fallback is on the cart dates, if any task-3570178 Forward-Port-Of: odoo/enterprise#49610
Original PR description
Before this commit, some tools of website_sale_renting were broken due to a loading problem of the overrides of the Variant mixin. For instance, the price on the product page was not depending on the rental period anymore. We now force them to be executed by prepending the js files in the manifest. Furthermore, the dates were not always given in the context. In this case, the fallback is on the cart dates, if any task-3570178 Forward-Port-Of: odoo/enterprise#49610
We add the activity plan and type menu to allows document managers to configure them. Also improve plan wording Task-3558929 Forward-Port-Of: odoo/enterprise#49414
Original PR description
We add the activity plan and type menu to allows document managers to configure them. Also improve plan wording Task-3558929 Forward-Port-Of: odoo/enterprise#49414
Steps: ---------------- - Open Field service - Select planning then by user - Group by project - The trace back is coming Issue: ---------- - when we trying to group by projects the trace back is raised Cause: --------- - By using of |= condition it collecting all the projects Fix: -- - Here by using of '|=' condition this will be collecting the all the projects,But actually we only fsm projects so we can use '&=' condition it will be helpfull for the getting only fsm p
Original PR description
Steps: ---------------- - Open Field service - Select planning then by user - Group by project - The trace back is coming Issue: ---------- - when we trying to group by projects the trace back is raised Cause: --------- - By using of |= condition it collecting all the projects Fix: -- - Here by using of '|=' condition this will be collecting the all the projects,But actually we only fsm projects so we can use '&=' condition it will be helpfull for the getting only fsm projects task-3522178 Forward-Port-Of: odoo/enterprise#48652
This commit fixes two alignment issues in the Knowledge sidebar. > Buttons with the same design having different styling to space the icon from the text ; > Buttons not being aligned with the rest of the sidebar element to the left. To fix these issues, we adapt our two buttons to make them use the same styling. We also have to adapt a bit the overall styling of the sidebar to allow our buttons to be correctly aligned to the left. task-3582600 Forward-Port-Of: odoo/enterprise#5
Original PR description
This commit fixes two alignment issues in the Knowledge sidebar. > Buttons with the same design having different styling to space the icon from the text ; > Buttons not being aligned with the rest of the sidebar element to the left. To fix these issues, we adapt our two buttons to make them use the same styling. We also have to adapt a bit the overall styling of the sidebar to allow our buttons to be correctly aligned to the left. task-3582600 Forward-Port-Of: odoo/enterprise#50189
This PR contains twos commits, one is an improvement on the composite reports and the second is a backport of this pr: https://github.com/odoo/enterprise/pull/49443. The goal of the first commit is to add a button on the reports next to the filters that will redirect to the configuration page of the report. On this page we have changed a placeholder and hide the use_section field in case the report has lines. While the backport adds the following improvements: - Automatic reload after
Original PR description
This PR contains twos commits, one is an improvement on the composite reports and the second is a backport of this pr: https://github.com/odoo/enterprise/pull/49443. The goal of the first commit is to add a button on the reports next to the filters that will redirect to the configuration page of the report. On this page we have changed a placeholder and hide the use_section field in case the report has lines. While the backport adds the following improvements: - Automatic reload after manual menuitem creation. - A UserError is raised when trying to create a duplicate menuitem. - Any existing menuitem is removed when deleting a report, or archived when archiving the report. task: 3569038 and 3422314 Forward-Port-Of: odoo/enterprise#50142
This PR adds a missing space between the image and its title in the kanban view of Frontdesk. Prior to this commit, the title of a drink within the kanban view of frontdesk had no spacing. This was not especially visible since the default images are using a white background, but this would become an issue as soon as the image stop having a white or transparent background. To prevent this unexpected renderer, we simply add a `ms-2` class to our title, ensuring it will always be spaced corre
Original PR description
This PR adds a missing space between the image and its title in the kanban view of Frontdesk. Prior to this commit, the title of a drink within the kanban view of frontdesk had no spacing. This was not especially visible since the default images are using a white background, but this would become an issue as soon as the image stop having a white or transparent background. To prevent this unexpected renderer, we simply add a `ms-2` class to our title, ensuring it will always be spaced correctly. task-3580511 | 17.0 | 17.0-frontdesk-add-missing-spacing-chgo | | ------------- | ------------- | | <img alt="image" src="https://github.com/odoo/enterprise/assets/128030743/df215d03-0ddd-4a07-ab3d-84dc01b47093"> | <img alt="image" src="https://github.com/odoo/enterprise/assets/128030743/6ef253b6-af05-4319-8ba2-8659a4dbf4d8"> | Forward-Port-Of: odoo/enterprise#50038
As of https://github.com/odoo/odoo/pull/114024, `display_name` is implicit in every form view (see the use of addFieldDependencies in the Form controller). Therefore, when you create a new record for this model, it calls the first `onchange`, which will compute display_name for a new record (id without origin). Some `_compute_display_name` don't handle new records correctly and raise a traceback. One is directly accessible: - Products > Open TaxCloud Category field > New => Traceback Other
Original PR description
As of https://github.com/odoo/odoo/pull/114024, `display_name` is implicit in every form view (see the use of addFieldDependencies in the Form controller). Therefore, when you create a new record for this model, it calls the first `onchange`, which will compute display_name for a new record (id without origin). Some `_compute_display_name` don't handle new records correctly and raise a traceback. One is directly accessible: - Products > Open TaxCloud Category field > New => Traceback Other models are inaccessible by default (no view to access or create a new record), but if someone creates a view for them with studio (or modifies an existing one to allow creation): - `product.avatax.category` - `social.post.template` Change the code of `_compute_display_name` on these models to be more defensive and avoid (potential) tracebacks. Community: https://github.com/odoo/odoo/pull/139592 Forward-Port-Of: odoo/enterprise#49721
Example of the issue: 1) Create a company called "main" 2) Create a branch for "main" called "branch" 3) Make an invoice in "main" 4) Make an invoice in "branch" 5) Modify the Aged Receivable report, and set filter_multi_company to 'disabled' 6) Select "main" as current company. By default, "branch" is selected as well, keep it like this. 7) Open the Aged Receivable ====> You only see the invoice made for "main", not the one in "branch". While totally correct in a regular multi-company
Original PR description
Example of the issue: 1) Create a company called "main" 2) Create a branch for "main" called "branch" 3) Make an invoice in "main" 4) Make an invoice in "branch" 5) Modify the Aged Receivable report, and set filter_multi_company to 'disabled' 6) Select "main" as current company. By default, "branch" is selected as well, keep it like this. 7) Open the Aged Receivable ====> You only see the invoice made for "main", not the one in "branch". While totally correct in a regular multi-company setup, this is not the behavior we want when those companies contain branches. When filter_multi_company only accepts the active company (so, when it's 'disabled' or set to 'tax_units' and no tax unit is selected), we also want to include all of its branches that are currently selected in the company selector. Forward-Port-Of: odoo/enterprise#50190 Forward-Port-Of: odoo/enterprise#49224
Forgot to remove a `console.log`. Forward-Port-Of: odoo/enterprise#50170
Original PR description
Forgot to remove a `console.log`. Forward-Port-Of: odoo/enterprise#50170
Forward-Port-Of: odoo/enterprise#50126
Original PR description
Forward-Port-Of: odoo/enterprise#50126
**Before this PR:** The 'Discard' button was colliding with the 'Save' button in the 'Create Workspace' wizard. **After this PR:** There will be proper space between both buttons. **Task**-3537818 Forward-Port-Of: odoo/enterprise#50108 Forward-Port-Of: odoo/enterprise#49701
Original PR description
**Before this PR:** The 'Discard' button was colliding with the 'Save' button in the 'Create Workspace' wizard. **After this PR:** There will be proper space between both buttons. **Task**-3537818 Forward-Port-Of: odoo/enterprise#50108 Forward-Port-Of: odoo/enterprise#49701
We currently have two date fields, "date" and "invoice_date". Before this pr, the "date" column was before the "invoice_date" field. We think it's more logical to have "invoice_date" before the other, since it's the legal date. What has been done: - Swap in the tree view the two columns - Swap in the search view the two columns Forward-Port-Of: odoo/enterprise#50107
Original PR description
We currently have two date fields, "date" and "invoice_date". Before this pr, the "date" column was before the "invoice_date" field. We think it's more logical to have "invoice_date" before the other, since it's the legal date. What has been done: - Swap in the tree view the two columns - Swap in the search view the two columns Forward-Port-Of: odoo/enterprise#50107
Add api.model flag to a function. It was forgotten in a last commit. Forward-Port-Of: odoo/enterprise#50102
Original PR description
Add api.model flag to a function. It was forgotten in a last commit. Forward-Port-Of: odoo/enterprise#50102
Clean the so.log generation code to be more readable. The code is also moved to the sale_order_log model. Forward-Port-Of: odoo/enterprise#43373
Original PR description
Clean the so.log generation code to be more readable. The code is also moved to the sale_order_log model. Forward-Port-Of: odoo/enterprise#43373
This commit changes the shortcut for the urgent tickets in the helpdesk dashboard view because this shortcut is now already used by the cog menu due to changes made in https://github.com/odoo/odoo/pull/140097. task-3560446 Forward-Port-Of: odoo/enterprise#50074 Forward-Port-Of: odoo/enterprise#49914
Original PR description
This commit changes the shortcut for the urgent tickets in the helpdesk dashboard view because this shortcut is now already used by the cog menu due to changes made in https://github.com/odoo/odoo/pull/140097. task-3560446 Forward-Port-Of: odoo/enterprise#50074 Forward-Port-Of: odoo/enterprise#49914
 Forward-Port-Of: odoo/enterprise#50115
Original PR description
 Forward-Port-Of: odoo/enterprise#50115
Adat tests following the changes of https://github.com/odoo/odoo/pull/140674 Task: 3580153 Forward-Port-Of: odoo/enterprise#50003
Original PR description
Adat tests following the changes of https://github.com/odoo/odoo/pull/140674 Task: 3580153 Forward-Port-Of: odoo/enterprise#50003
When having multi company (with branches and tax units) it may sometimes be a bit difficult for the user to realize what companies are currently used by the report. This commit adds under the filters, on top of the report the names of the companies present in the options dict with the key companies under certain conditions. task: 3573675 Forward-Port-Of: odoo/enterprise#49825
Original PR description
When having multi company (with branches and tax units) it may sometimes be a bit difficult for the user to realize what companies are currently used by the report. This commit adds under the filters, on top of the report the names of the companies present in the options dict with the key companies under certain conditions. task: 3573675 Forward-Port-Of: odoo/enterprise#49825
In the French balance sheet, there are two lines called Report à Nouveau and Résultat de l'Exercice. The normal accounting practice is to: - at year end, debit the Unaffected Earnings account and credit the Résultat de l'Exercice account - at the affectation of earnings (which typically happens 3-4 months after year end), debit the Résultat de l'Exercice account and credit the Reserves, Dividends and Report à Nouveau accounts. This commit aims to handle those two lines in a sensible way
Original PR description
In the French balance sheet, there are two lines called Report à Nouveau and Résultat de l'Exercice. The normal accounting practice is to: - at year end, debit the Unaffected Earnings account and…
In the French balance sheet, there are two lines called Report à Nouveau and Résultat de l'Exercice.
The normal accounting practice is to:
- at year end, debit the Unaffected Earnings account and credit the Résultat de l'Exercice account
- at the affectation of earnings (which typically happens 3-4 months after year end), debit the Résultat de l'Exercice account and credit the Reserves, Dividends and Report à Nouveau accounts.
This commit aims to handle those two lines in a sensible way for real-time accounting:
- the Résultat de l'Exercice line always corresponds to the current year's effective Résultat de l'Exercice (thanks to the cross-report to the P&L)
- the Report à Nouveau line is composed of:
- previous years' earnings that were not affected by a closing entry to any equity account,
- the balance of the Résultat de l'Exercice account, which contains earnings from previous years that were closed, but have not been affected to any other Equity account, and
- the balance of the Report à Nouveau account proper.
Task: 3288626
Forward-Port-Of: odoo/enterprise#42351Adapts tests to support sending to preparation display. task-id: 3568361 related: https://github.com/odoo/odoo/pull/140092 Forward-Port-Of: odoo/enterprise#49731
Original PR description
Adapts tests to support sending to preparation display. task-id: 3568361 related: https://github.com/odoo/odoo/pull/140092 Forward-Port-Of: odoo/enterprise#49731
In this commit: https://github.com/odoo/enterprise/pull/50142/commits/1df7c45a2f56a70ae7d1d4aa90f9d0aa1a34cd36 We added a button next to the filters that will redirect to the configuration page of the report. The problem was that only the cogs was clickable and not the surrounding background. Forward-Port-Of: odoo/enterprise#50248
Original PR description
In this commit: https://github.com/odoo/enterprise/pull/50142/commits/1df7c45a2f56a70ae7d1d4aa90f9d0aa1a34cd36 We added a button next to the filters that will redirect to the configuration page of the report. The problem was that only the cogs was clickable and not the surrounding background. Forward-Port-Of: odoo/enterprise#50248
Issus on several tests in test_monthly_declaration.py due to account_representative_id called in l10n_lu_hr_payroll. This field depends on action report installed with l10n_lu_reports. Forward-Port-Of: odoo/enterprise#49991
Original PR description
Issus on several tests in test_monthly_declaration.py due to account_representative_id called in l10n_lu_hr_payroll. This field depends on action report installed with l10n_lu_reports. Forward-Port-Of: odoo/enterprise#49991
Before correction : The function _get_representation_fees_threshold used a field from hr_job. But this field exist only if l10n_be_hr_contract_salary is installed After correction : Put the behaviour of this function linked to this field in l10n_be_hr_contract_salary. Forward-Port-Of: odoo/enterprise#49999
Original PR description
Before correction : The function _get_representation_fees_threshold used a field from hr_job. But this field exist only if l10n_be_hr_contract_salary is installed After correction : Put the behaviour of this function linked to this field in l10n_be_hr_contract_salary. Forward-Port-Of: odoo/enterprise#49999
[FIX] account_reports: totals below To add a total below line, we go through all the lines and check if the current line id does **not** start with the total below parent id line. If it's the case, we add it before adding the line. This makes sense because the total below should be the last child of a line. The problem is that you may have cases where the line id start with the total below parent id even tho they are not related. For example, if the line id is something like x|y-14 an
Original PR description
[FIX] account_reports: totals below To add a total below line, we go through all the lines and check if the current line id does **not** start with the total below parent id line. If it's the case, we add it before adding the line. This makes sense because the total below should be the last child of a line. The problem is that you may have cases where the line id start with the total below parent id even tho they are not related. For example, if the line id is something like x|y-14 and the total below parent id is x|y-1. To fix it, we check if the line id does **not** start with the total below parent id **ending with** the line id hierarchy separator. [REF] account_reports: line id hierarchy delimiter Replaces the line id hierarchy delimiter `|` used in the construction of line ids by a constant named LINE_ID_HIERARCHY_DELIMITER with the same value. Forward-Port-Of: odoo/enterprise#49971 Forward-Port-Of: odoo/enterprise#49804
The aim of this commit is fixing the asynchronous flow to get what we want since the beginning. A first version(https://github.com/odoo-dev/enterprise/commit/ed7d7486f30e076e6040a2d528a2c4926225bfa9) of the flow only adds the call to the cron to make the transactions fetch asynchronous. This first version doesn't update the status on the user dashboard. It means that the spin turns until the user refresh his/her dashboard. Now the dashboard is automatically updated by websocket once we
Original PR description
The aim of this commit is fixing the asynchronous flow to get what we want since the beginning. A first version(https://github.com/odoo-dev/enterprise/commit/ed7d7486f30e076e6040a2d528a2c4926225bfa9)…
The aim of this commit is fixing the asynchronous flow to get what we want since the beginning. A first version(https://github.com/odoo-dev/enterprise/commit/ed7d7486f30e076e6040a2d528a2c4926225bfa9) of the flow only adds the call to the cron to make the transactions fetch asynchronous. This first version doesn't update the status on the user dashboard. It means that the spin turns until the user refresh his/her dashboard. Now the dashboard is automatically updated by websocket once we receive a response from Odoo Fin (if we receive an error or if we fetch or not some transactions). We're using the field connection_state_details on account.online.link (added by this commit: https://github.com/odoo-dev/enterprise/commit/4e88e4ff87338b36baf317194c1a52ba57da35cd) to save the last connection state (how many transactions we fetched or the error). The field is on the wrong model. We probably have to improve that in master. This commit also adds a new cron for connection with a fetching_status set to "waiting". This cron should only be used to fetch transactions asynchronously. When a user receives a new connection state, it's saved on the connection, once the user opens the bank statement lines view, this state is "consumed", meaning that we remove this state from the connection. This commit also changes how the function "_fetch_transactions" works. Now, we're trying to refresh all accounts, if we have at least one account ready to synchronize, we call the cron to fetch transactions asynchronously. task-3568712 Forward-Port-Of: odoo/enterprise#49776
Before this commit, when a draft subscription is created, the price unit does not update in the following flow: 1) create a draft subscription 2) add a recurring product 3) update that line's product to another (non recurring) with another list price. The price is not updated. taskid: 3551308 Forward-Port-Of: odoo/enterprise#49836 Forward-Port-Of: odoo/enterprise#48873
Original PR description
Before this commit, when a draft subscription is created, the price unit does not update in the following flow: 1) create a draft subscription 2) add a recurring product 3) update that line's product to another (non recurring) with another list price. The price is not updated. taskid: 3551308 Forward-Port-Of: odoo/enterprise#49836 Forward-Port-Of: odoo/enterprise#48873