Monday, November 8, 2021
36 changes · master
New functionality added to Odoo
HR teams can now view a dedicated report showing each employee's skills. This makes it easier to understand workforce capabilities and support staffing, development, and planning decisions.
Original PR description
Adds a report showing the skills per employee. TaskID: 2677101 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
Enhancements to existing features
The mail area now handles attachment box actions through the underlying conversation data model instead of the visible page components. This makes attachment behavior more consistent and easier to maintain, with little direct change expected for users.
Original PR description
Part of task-2579306
Resolved issues and error corrections
This change removes an unnecessary import from the web testing helper code. It has no direct effect on users, but keeps the codebase cleaner and easier to maintain.
Original PR description
This commit removes a useless import from the tests helper. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Features or functions removed from Odoo
This update removes old Point of Sale code that was no longer used, including an obsolete on-screen keyboard library and an unnecessary product category breadcrumb component. This helps keep the system cleaner and easier to maintain without changing day-to-day POS behavior.
Original PR description
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
Miscellaneous changes
Description of the issue/feature this PR addresses: Current behavior before PR: The transfer line order makes no sense for a picker (it's in the order of the creation of the line) And the printing report of the batch transfer is on too many pages, it's one page by location, but we always group on 'from location'. Desired behavior after PR is merged: We want to have the lines of the detailed operation in the same order as the picker will be picking the products, so we order by source l
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: The transfer line order makes no sense for a picker (it's in the order of the creation of the line) And the printing report of the batch transfer is on too many pages, it's one page by location, but we always group on 'from location'. Desired behavior after PR is merged: We want to have the lines of the detailed operation in the same order as the picker will be picking the products, so we order by source location, destination location, sequence and then by id (i.e. creation time) For the printing report of the bath transfer, it would be better not to split by location and keep the report on the less page possible. task-2496324 odoo/enterprise#21921 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79069
This update improves wording around chart template accounts so their purpose is easier to understand. It also removes an outdated internal comment that could cause confusion for future maintenance, with no expected change to day-to-day accounting workflows.
Original PR description
The commit also delete obsolete comment "Set default cash difference account on company" which meant to be for another code, not for creating of suspense accounts 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
When leads are converted into helpdesk tickets, or tickets into leads, marketing tracking information is now preserved. This helps teams keep accurate campaign attribution across CRM and Helpdesk workflows, while also simplifying the conversion form when only one helpdesk team is available.
Original PR description
Information about UTM codes was lost when converting leads to helpdesk tickets and vice versa. This commit ensures that they are correctly propagated. The Python test suite is completed to reflect this. As specific processes are in place to create Helpdesk Teams and Ticket Types, they can no longer be created nor edited on the fly in this conversion process. To accelerate form completion in case there is a single helpdesk team to chose from, this field will be automatically completed on the Lead to Ticket wizard form. Task-2671664
The employee form now counts time off in the same way as the time off dashboard, including all requests that are not cancelled or refused. This avoids confusing differences between screens and gives managers and employees a more reliable view of remaining time off.
Original PR description
Description of the issue/feature this PR addresses: The holidays count on the employee form is not consistent with the count on the dashboard. The count on the employee form counts the holidays left based on the approved holiday. The count on the time off dashboard counts all the holidays that are not cancelled or refused. The time off counts should be consistent across the different screens. Current behavior before PR: The employee form smart button displays the count of time off based on the approved time off The time off dashboard displays the count of time off based on the time off that are not cancelled or refused Desired behavior after PR is merged: The count of time off is consistent across the different screens with the time off count based on the time off that are not cancelled or refused Task-2670658 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes swipe actions so they work correctly for right-to-left languages, inside scrollable content, and with content that previously affected layout height. This improves reliability for mobile interactions, including cases like emails with wide formatted content.
Original PR description
This commit fixes issues with the ActionSwiper component. The first issue was due to the lack of rtl support when using the component to perform actions because the actions were not inverted as they should be. Now, instead of using props directly, we use localizedProps that will change depending of the language direction. A test has been added, and the test is now located in a folder for core components. The second issue that has been fixed is about the swiper not having the right height because of overflow issues. A div now wraps the content to hide only the overflow-x property without affecting the y axis. Finally, the swiper now behaves correcly when scrollables areas are under touch manipulation. Now, the element can be swiped when all scrollables areas have reached their limit. e.g. This bug was preventing interaction with emails formatted with elements larger than the actual email. A test has been written to assure that use case.
In a multi-company and multi-currency environment, the computation of the purchase price may be based on the incorrect company (and thus lead to incorrect results) To reproduce the issue: (Use demo data) 1. In Settings: - Enable "Multi-Currencies" 2. Update "My Company (Chicago)": - Currency: EUR 3. Edit currencies' rate for all companies(!): - USD: 1.0 - EUR: 3.0 4. Create a product category PC: - Costing Method: FIFO 5. Create a product P: - Type: Stora
Original PR description
In a multi-company and multi-currency environment, the computation of the purchase price may be based on the incorrect company (and thus lead to incorrect results) To reproduce the issue: (Use demo…
In a multi-company and multi-currency environment, the computation of
the purchase price may be based on the incorrect company (and thus lead
to incorrect results)
To reproduce the issue:
(Use demo data)
1. In Settings:
- Enable "Multi-Currencies"
2. Update "My Company (Chicago)":
- Currency: EUR
3. Edit currencies' rate for all companies(!):
- USD: 1.0
- EUR: 3.0
4. Create a product category PC:
- Costing Method: FIFO
5. Create a product P:
- Type: Storable
- Category: PC
6. Switch to "My Company (Chicago)"
- Note that in this company, the costing method of PC is "Standard
Price"
7. Edit P:
- Cost: 10
8. Create a sale order SO:
- Pricelist: EUR
- Lines (add Cost columns):
- 1 x P (Note that cost is 10€)
9. Confirm SO
Error: The sale order line is incorrect, the cost is now 30€. A rate
conversion has been applied on the amount
In `_compute_purchase_price`, several fields/methods depend on the SOL's
company: `property_cost_method`, `_compute_average_price`,
`cost_currency_id`. Therefore, we should include this specific company
in the environment of the product
OPW-2659265
Forward-Port-Of: odoo/odoo#79350
Forward-Port-Of: odoo/odoo#78743When exporting, the delivery address is put inside the xml. This field is added by the 'sale' module and is not supposed to be displayed for vendor bill. However, even if this field isn't displayed, the factur-x module was setting the wrong delivery address on it. issue: 2668902 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79304 Forward-Port-Of: odoo/odoo#79179
Original PR description
When exporting, the delivery address is put inside the xml. This field is added by the 'sale' module and is not supposed to be displayed for vendor bill. However, even if this field isn't displayed, the factur-x module was setting the wrong delivery address on it. issue: 2668902 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79304 Forward-Port-Of: odoo/odoo#79179
Prior to this commit sale_order_id filter was shown as `Sales Order Item`. After this commit: sale_order_id filter is shown as `Sales Order`. task-2685356 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79420
Original PR description
Prior to this commit
sale_order_id filter was shown as `Sales Order Item`.
After this commit:
sale_order_id filter is shown as `Sales Order`.
task-2685356
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#79420Issue: When trying to print a Swiss QR bill, if multiple images are presents in document, and they have an URL as src, some pictures will not be displayed. (Same issue may occur with simple QR code) Cause: It's a known issue with wkhtmltopdf: odoo@2949138 Also, adding CSS class to body by JS break wkhtmltopdf. Solution: Replace link by base64 image value (use a function to retrieve base64 image instead of image_url). Remove class 'l10n_ch_qr' added by js (n
Original PR description
Issue: When trying to print a Swiss QR bill, if multiple images are presents in document, and they have an URL as src, some pictures will not be displayed. (Same issue may occur with simple QR code) Cause: It's a known issue with wkhtmltopdf: odoo@2949138 Also, adding CSS class to body by JS break wkhtmltopdf. Solution: Replace link by base64 image value (use a function to retrieve base64 image instead of image_url). Remove class 'l10n_ch_qr' added by js (no need since CSS file dedicated to this report). Extra: Alter some CSS for better rendering. opw-2620082 Forward-Port-Of: odoo/odoo#77423 Forward-Port-Of: odoo/odoo#75408
Before this commit, when inserting a new snippet or moving a snippet that was already in the page would temporarily create hooks (`we-hook`) in the page. The insertion of thoses hooks would trigger mutation in the dirty observer (observer defined in edit.js) and mark all oe_structure for which a hook was temporarily inserted. Thus, creating unnecessary views in the backend. Now, the code skip the mutations of the drag and drop hooks. Task-2567752 Description of the issue/feature th
Original PR description
Before this commit, when inserting a new snippet or moving a snippet that was already in the page would temporarily create hooks (`we-hook`) in the page. The insertion of thoses hooks would trigger mutation in the dirty observer (observer defined in edit.js) and mark all oe_structure for which a hook was temporarily inserted. Thus, creating unnecessary views in the backend. Now, the code skip the mutations of the drag and drop hooks. Task-2567752 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#79373 Forward-Port-Of: odoo/odoo#78978
…tion We want to activate product variant by default for testing product configurator. Otherwise Odoo want to de-install the whole module due to dependency chain. Task-2677144 Forward-Port-Of: odoo/odoo#79353
Original PR description
…tion We want to activate product variant by default for testing product configurator. Otherwise Odoo want to de-install the whole module due to dependency chain. Task-2677144 Forward-Port-Of: odoo/odoo#79353
Description of the issue/feature this PR addresses: Modifications needed to create electronic vendor bill document type (46) since it is mandatory for some customers in Chile Adds new account to withhold vat tax, and new vat tax Enables document type 46 Allow electronic docs in purchase journals [FIX] l10n_latam_invoice_document Consider doc type 46 as a vendor document More information -> https://www.sii.cl/preguntas_frecuentes/catastro/001_012_3665.htm Current behavior before PR: Inv
Original PR description
Description of the issue/feature this PR addresses: Modifications needed to create electronic vendor bill document type (46) since it is mandatory for some customers in Chile Adds new account to withhold vat tax, and new vat tax Enables document type 46 Allow electronic docs in purchase journals [FIX] l10n_latam_invoice_document Consider doc type 46 as a vendor document More information -> https://www.sii.cl/preguntas_frecuentes/catastro/001_012_3665.htm Current behavior before PR: Invoices type 46 (chile) cannot be used in vendor bills. The taxes and account needed are not present in the plan Desired behavior after PR is merged: integrates with l10n_cl_edi allowing type 46 This replaces #75970 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#77570
- fix updating context cannot recompute _compute_leaves method Description of the issue/feature this PR addresses: - Select multiple hr.leave.allocation and use export function will export a wrong leaves_taken Current behavior before PR: - leaves_taken will not compute again even provide different context Desired behavior after PR is merged: - leaves_taken should be computed correctly based on the context -- I confirm I have signed the CLA and read the PR guidelines at www.od
Original PR description
- fix updating context cannot recompute _compute_leaves method Description of the issue/feature this PR addresses: - Select multiple hr.leave.allocation and use export function will export a wrong leaves_taken Current behavior before PR: - leaves_taken will not compute again even provide different context Desired behavior after PR is merged: - leaves_taken should be computed correctly based on the context -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#78794
This PR ---------- In comparison to the Chart of Account in Viet Nam, your Vietnamese translation is wrong. So, I want to contributor for you. Plz review !!! You can refer to here: https://erponline.vn/blog/blog-5/post/vietnam-chart-of-accounts-under-the-vietnamese-accounting-standards-99 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79341
Original PR description
This PR ---------- In comparison to the Chart of Account in Viet Nam, your Vietnamese translation is wrong. So, I want to contributor for you. Plz review !!! You can refer to here: https://erponline.vn/blog/blog-5/post/vietnam-chart-of-accounts-under-the-vietnamese-accounting-standards-99 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79341
Expected behaviour: When you create a sale order with a project associated. When the sale order change state from non upsell to upsell sales person should receive one email. Current behaviour: The sales person receive an email for every entry in the timesheet after the sale order goes from non upsell to upsell. Step to reproduce: Create a sale order setup to create a project and task and the invoicing policy is ordered quantities. Add a timesheet entry which takes it past the order
Original PR description
Expected behaviour: When you create a sale order with a project associated. When the sale order change state from non upsell to upsell sales person should receive one email. Current behaviour: The sales person receive an email for every entry in the timesheet after the sale order goes from non upsell to upsell. Step to reproduce: Create a sale order setup to create a project and task and the invoicing policy is ordered quantities. Add a timesheet entry which takes it past the ordered quantity. Create the invoice for the order. The state of the line and order goes to upsell, and the upsell email is sent to the salesperson. Add another line in the timesheet and the email is sent again to the salesperson opw-2581428 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79375 Forward-Port-Of: odoo/odoo#79287
Since the Time Off B2B, the deduct extra hours didn't work anymore due to an invalid domain. This commit fixes the traceback but also the behaviour as the domain did not make any sense anymore. TaskId-2658077 Forward-Port-Of: odoo/odoo#78200
Original PR description
Since the Time Off B2B, the deduct extra hours didn't work anymore due to an invalid domain. This commit fixes the traceback but also the behaviour as the domain did not make any sense anymore. TaskId-2658077 Forward-Port-Of: odoo/odoo#78200
**Description of the issue/feature this PR addresses:** When the product configurator option is enabled and a product that has no variants but has optional products is opened, there are two modals one on top of the other because of an extra trigger of a handler. **Current behavior before PR:** The modal shows up twice, and needs to be closed twice. **Desired behavior after PR is merged:** The modal only shows up once and behaves as expected. opw-2678887 -- I confirm I have s
Original PR description
**Description of the issue/feature this PR addresses:** When the product configurator option is enabled and a product that has no variants but has optional products is opened, there are two modals one on top of the other because of an extra trigger of a handler. **Current behavior before PR:** The modal shows up twice, and needs to be closed twice. **Desired behavior after PR is merged:** The modal only shows up once and behaves as expected. opw-2678887 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79300
1. Configure MX company, make sure testing certificate and vat are loaded into the company 2. Sign an invoice with 16% included in price No errors will be shown but opening the resulting CFDI xml will show a discount "Descuento" equal to the tax amount, which is incorrect opw-2665082 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.od
Original PR description
1. Configure MX company, make sure testing certificate and vat are loaded into the company 2. Sign an invoice with 16% included in price No errors will be shown but opening the resulting CFDI xml will show a discount "Descuento" equal to the tax amount, which is incorrect opw-2665082 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#79308 Forward-Port-Of: odoo/odoo#79018
Current Behaviour : Go to Time off -> Approvals -> Time Off -> create one time off of type 'Annual Time Off 2021' for employees Anita, Abigail and Audrey -> validate -> refuse -> set to draft -> Traceback Behaviour after the PR : No traceback opw-26842777 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79402
Original PR description
Current Behaviour : Go to Time off -> Approvals -> Time Off -> create one time off of type 'Annual Time Off 2021' for employees Anita, Abigail and Audrey -> validate -> refuse -> set to draft -> Traceback Behaviour after the PR : No traceback opw-26842777 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79402
Some variables were used in _t function instead of raw strings. One string was not translated properly. task-2686066 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79465
Original PR description
Some variables were used in _t function instead of raw strings. One string was not translated properly. task-2686066 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79465
On tablet, the call-to-action to install the app shouldn't show the QR code... to be scanned by the tablet itself. This commit fixes it by using the platform detection instead of the screen size. Steps to reproduce: - Open "Expenses" on tablet - ensure no records are listed (use filters if needed) - click on the call-to-action to one of the app store => opens the QR code's modal instead of going directly to the store task-2349194 Forward-Port-Of: odoo/odoo#78638
Original PR description
On tablet, the call-to-action to install the app shouldn't show the QR code... to be scanned by the tablet itself. This commit fixes it by using the platform detection instead of the screen size. Steps to reproduce: - Open "Expenses" on tablet - ensure no records are listed (use filters if needed) - click on the call-to-action to one of the app store => opens the QR code's modal instead of going directly to the store task-2349194 Forward-Port-Of: odoo/odoo#78638
Reproduce : (With timezone GMT+3) - Create any record R1 with previous day's date and time after 21:00. - Create any record R2 with today's date and time after 21:00. - Create a filter to show all todays records (Date is between "<TODAY'S DATE> 00:00:00 and <TODAY'S DATE> 23:59:59". Result : Even though R1 is in yesterday's date, it will show in the list. R2 will not show in this list. Explanation : This behaviour has been observed in several modules, for any timezone but UTC
Original PR description
Reproduce : (With timezone GMT+3) - Create any record R1 with previous day's date and time after 21:00. - Create any record R2 with today's date and time after 21:00. - Create a filter to show all…
Reproduce : (With timezone GMT+3) - Create any record R1 with previous day's date and time after 21:00. - Create any record R2 with today's date and time after 21:00. - Create a filter to show all todays records (Date is between "<TODAY'S DATE> 00:00:00 and <TODAY'S DATE> 23:59:59". Result : Even though R1 is in yesterday's date, it will show in the list. R2 will not show in this list. Explanation : This behaviour has been observed in several modules, for any timezone but UTC & only with custom filters default datetime values. The search was applied on [datetime(UTC) + 2 * offset] because the timezone wasn't correctly set. Solution : Timezone is now correctly set on default datetime values. 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#79008 Forward-Port-Of: odoo/odoo#75663
Since https://github.com/odoo/odoo/commit/ebf8d67485f7f71f6eb51762298cf50c5835ee08 design-themes repo is not excluded from the cloc count. The module website_animate that was used as beacon to identify the folder that contains the design-themes as been merged into website. We need a new one, theme_common seems a reasonable candidate -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79483
Original PR description
Since https://github.com/odoo/odoo/commit/ebf8d67485f7f71f6eb51762298cf50c5835ee08 design-themes repo is not excluded from the cloc count. The module website_animate that was used as beacon to identify the folder that contains the design-themes as been merged into website. We need a new one, theme_common seems a reasonable candidate -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#79483
### Steps to reproduce - Install Field Service app (do **not** install `fsm_report`) - Create a product with an external id `field_service_product` for the model `industry_fsm` (-> `industry_fsm.field_service_product`) - Try to install `fsm_report` ### Reason In `industry_fsm_report/__init__.py`, we're checking for a ref that doesn't exist anymore since dependency breaking (commit : a9747c6c011a5f608ebd82e8f37b1519e2590480). Should go to `industry_fsm_sale_report` instead (seen with **ltu
Original PR description
### Steps to reproduce - Install Field Service app (do **not** install `fsm_report`) - Create a product with an external id `field_service_product` for the model `industry_fsm` (-> `industry_fsm.field_service_product`) - Try to install `fsm_report` ### Reason In `industry_fsm_report/__init__.py`, we're checking for a ref that doesn't exist anymore since dependency breaking (commit : a9747c6c011a5f608ebd82e8f37b1519e2590480). Should go to `industry_fsm_sale_report` instead (seen with **ltu**). OPW-2637645 Forward-Port-Of: odoo/enterprise#21897
Recreate a mps with bom for a product doesn't work if the current mps in database doesn't have the bom_id set. task-2678070 Forward-Port-Of: odoo/enterprise#21893
Original PR description
Recreate a mps with bom for a product doesn't work if the current mps in database doesn't have the bom_id set. task-2678070 Forward-Port-Of: odoo/enterprise#21893
…and sms and base_address_extended Currently, a view present in `l10n_be_reports` depends on the `sms` module. But `sms` is not a dependancy of `l10n_be_reports`. This is why this module is created. The same also applies to `base_address_extended`. Related PR : odoo/upgrade#3012 Forward-Port-Of: odoo/enterprise#21982
Original PR description
…and sms and base_address_extended Currently, a view present in `l10n_be_reports` depends on the `sms` module. But `sms` is not a dependancy of `l10n_be_reports`. This is why this module is created. The same also applies to `base_address_extended`. Related PR : odoo/upgrade#3012 Forward-Port-Of: odoo/enterprise#21982
Before this commit it is not possible to override/change or add values when creating a calendar.event item. By splitting this up in a subfunction we could easily inherit this and still insert or modify values without having to override the whole (which is big) controller function Forward-Port-Of: odoo/enterprise#22079 Forward-Port-Of: odoo/enterprise#21806
Original PR description
Before this commit it is not possible to override/change or add values when creating a calendar.event item. By splitting this up in a subfunction we could easily inherit this and still insert or modify values without having to override the whole (which is big) controller function Forward-Port-Of: odoo/enterprise#22079 Forward-Port-Of: odoo/enterprise#21806
1. Configure MX company, make sure testing certificate and vat are loaded into the company 2. Sign an invoice with 16% included in price No errors will be shown but opening the resulting CFDI xml will show a discount "Descuento" equal to the tax amount, which is incorrect opw-2665082 Forward-Port-Of: odoo/enterprise#22069 Forward-Port-Of: odoo/enterprise#21673
Original PR description
1. Configure MX company, make sure testing certificate and vat are loaded into the company 2. Sign an invoice with 16% included in price No errors will be shown but opening the resulting CFDI xml will show a discount "Descuento" equal to the tax amount, which is incorrect opw-2665082 Forward-Port-Of: odoo/enterprise#22069 Forward-Port-Of: odoo/enterprise#21673
Steps to reproduce the bug: - install delivery_bpost and sale_management - Connect as Belgian company - Create a SO: - Select any Belgian customer - Add any storable product - Click on “Add Shipping” and select “Bpost Domestic bpack 24h Pro” - Confirm the SO - Try to validate the delivery Problem: A traceback is triggered, because before this commit: https://github.com/odoo/odoo/commit/5913b7265ef5bd8a01a882fa0977bbd64321054d the XML was decoded via the `decode` function
Original PR description
Steps to reproduce the bug:
- install delivery_bpost and sale_management
- Connect as Belgian company
- Create a SO:
- Select any Belgian customer
- Add any storable product
- Click on “Add Shipping” and select “Bpost Domestic bpack 24h Pro”
- Confirm the SO
- Try to validate the delivery
Problem:
A traceback is triggered, because before this commit: https://github.com/odoo/odoo/commit/5913b7265ef5bd8a01a882fa0977bbd64321054d
the XML was decoded via the `decode` function, but now we use `Markup` to clean up the string,
so we do not need to decode the string.
opw-2684331
Forward-Port-Of: odoo/enterprise#22136Add document type 46 to _is_doc_type_voucher method to modify the account.move view to allow doc type 46 in selector After this PR Odoo will be able to issue "Factura de compra" (SII code 46). This targets saas-14.5 instead of master (replaces PR #20616) And is related to https://github.com/odoo/odoo/pull/77570 Forward-Port-Of: odoo/enterprise#21334
Original PR description
Add document type 46 to _is_doc_type_voucher method to modify the account.move view to allow doc type 46 in selector After this PR Odoo will be able to issue "Factura de compra" (SII code 46). This targets saas-14.5 instead of master (replaces PR #20616) And is related to https://github.com/odoo/odoo/pull/77570 Forward-Port-Of: odoo/enterprise#21334
PURPOSE Open studio when Design Worksheet Template button is clicked in Worksheet Template form. SPEC Clicking on Design Worksheet Template button should open studio. TASK 2593520 Forward-Port-Of: odoo/enterprise#20414
Original PR description
PURPOSE Open studio when Design Worksheet Template button is clicked in Worksheet Template form. SPEC Clicking on Design Worksheet Template button should open studio. TASK 2593520 Forward-Port-Of: odoo/enterprise#20414
Description of the issue/feature this PR addresses: Current behavior before PR: The transfer line order has no sense for a picker (it's in the order of the creation of the line) Desired behavior after PR is merged: We want to have the line of the detailed operation in the same order as the picker will be picking the But since the behavior as changed, we need some tweaks in the tests. task-2496324 odoo/odoo#79069 -- I confirm I have signed the CLA and read the PR guidelines at ww
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: The transfer line order has no sense for a picker (it's in the order of the creation of the line) Desired behavior after PR is merged: We want to have the line of the detailed operation in the same order as the picker will be picking the But since the behavior as changed, we need some tweaks in the tests. task-2496324 odoo/odoo#79069 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#21921