Daily updates from Odoo
Wednesday, November 27, 2024
34 changes · 18.0
Security fixes and vulnerability patches
This update limits access to the Indonesian employee tax status field so it is no longer publicly visible. It helps protect sensitive payroll-related employee information and resolves related build errors.
Original PR description
Giving l10n_id_kode_ptkp a group value, as it is not supposed to be public. [broken error builds](https://runbot.odoo.com/web/#id=75156&menu_id=424&cids=1&action=573&model=runbot.build.error&view_type=form)
Enhancements to existing features
This update adds the base payment data needed for Kueski Pay to be available for installation in Odoo. It prepares the system so businesses can later enable this payment option once the related provider integration is installed.
Original PR description
Description of the issue/feature this PR addresses: This commit adds the necessary data into payment to install kueski pay payment provider. task-3907297 Current behavior before PR: Kueski Pay didn't exist. Desired behavior after PR is merged: Kueski Pay now is ready to install later on Enterprise PR: https://github.com/odoo/enterprise/pull/73531 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail chat interface has been visually refined with larger, rounder chat windows, subtler controls, clearer message timing, and improved separators and banners. These updates make conversations easier to scan and reduce visual clutter without changing the underlying messaging workflow.
Original PR description
- chat windows are larger, removed option to resize chat windows - chat window header commands: compacter, less visible - message actions: less visible when not hovered, no border on click - new message banner slightly smaller and warning style, text bolder - HH:mm on non-squashed message for datetime - slightly smaller and less visible datetime on message - horizontal padding on date section and new message separator - date section has shorter month name - chat window is rounder, bottom is rounded too - jump to present button reduced border opacity + shadow-sm added Backport of https://github.com/odoo/odoo/pull/187654 Before  After 
Odoo can now retrieve official exchange rates from the Hungarian National Bank. This helps Hungarian companies keep currency rates aligned with their national bank source and reduces manual updates.
Original PR description
Objective
---------
Many countries want to use the official rates provided by their National
Bank in their database. A lot of them were already implemented, and now
it's the turn of the Hungarian National Bank.
Solution
---------
The MNB has implemented a SOAP service to access the latest rates.
The service is available at this address
http://www.mnb.hu/arfolyamok.asmx?wsdl
and the service operation `GetCurrentExchangeRates()`
returns:
```xml
<MNBCurrentExchangeRates>
<Day date="2024-11-20">
<Rate unit="1" curr="AUD">252,78</Rate>
<Rate unit="1" curr="BGN">209,49</Rate>
<Rate unit="1" curr="BRL">67,24</Rate>
...
</Day>
</MNBCurrentExchangeRates>
```
Therefore, we can:
1. Open a Zeep client to communicate with the service
2. Parse the XML and fetch the data (currency, ratio, rates and date).
3. Update the result dict accordingly
task-4320506Resolved issues and error corrections
This fixes an issue in automated website editor walkthroughs where actions could lose track of earlier input changes between steps. Keeping the action context consistent from the start makes these tours more reliable and helps prevent false test failures around link editing.
Original PR description
The setupEventActions defines an element (environment) in which the history of actions is retained. If this element changes at each step of the tour, then it is for example not possible to "blur" a previously altered input. This environment must be defined at the beginning of the tour.
The portal chatter setup no longer shows an error just because a user cannot access a related discussion at initialization. Access is still checked when messages are actually loaded, reducing false failures while preserving the normal permission checks.
Original PR description
Since the `chatter_init` route is only responsible for checking the valid partner in the case of a public user, there is no need to raise `NotFound` if there is no access to the thread. Checking for access to the thread and raise if it's needed is done when fetching the messages. reported on [this build error](https://runbot.odoo.com/web/#id=99087&menu_id=405&cids=1&model=runbot.build.error&view_type=form)
This fix ensures that when inventory tracking is disabled for a product, the hidden Lot/Serial Number valuation setting is also turned off. This prevents confusing receipt errors that incorrectly ask users to enter serial numbers for products that are no longer tracked.
Original PR description
**Steps to reproduce the bug:**
- Create a storable product “P1”:
- Set it to be tracked by Serial Number (SN).
- Enable Valuation by Lot/SN.
- Save.
- Disable inventory tracking.
**Problem:**
The Valuation by Lot/SN option becomes invisible but is not actually disabled. For example, when processing a receipt, a user error occurs, requiring a serial number to be set.
opw-4330877This fix prevents an error when a point of sale receipt printer connected through an IoT box is unavailable and staff choose browser printing instead. The receipt should now open the browser print dialog as expected, helping sales continue without interruption.
Original PR description
Introduced in #184138. When you try to print a receipt using an IoT box that isn't available, there is the option to print using the browser as a fallback. However, clicking this option produces a traceback. Steps to reproduce: - Configure a POS to use an IoT Box Receipt Printer (e.g. the default [Shop] Receipt Printer) - Make sure the IoT box is not reachable - Make an order and try to print the receipt, it should fail and the dialog will appear asking if you would like to use the web printer - Select OK, and a traceback will appear Expected behaviour: - There is no traceback and the browser printing dialog appears --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an error that could stop users from sending point-of-sale receipts through WhatsApp. The receipt-sending flow now handles the expected receipt image information correctly, helping staff share receipts without interruption.
Original PR description
Currently, an exception is generated when the user tries to send a POS order receipt on WhatsApp. Error ``` TypeError: PosOrder.action_sent_receipt_on_whatsapp() takes 3 positional arguments but 4…
Currently, an exception is generated when the user tries to send a POS order receipt on WhatsApp.
Error
```
TypeError: PosOrder.action_sent_receipt_on_whatsapp() takes 3 positional arguments but 4 were given
File "odoo/http.py", line 2363, in __call__
response = request._serve_db()
File "odoo/http.py", line 1891, in _serve_db
return self._transactioning(
File "odoo/http.py", line 1954, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 137, in retrying
result = func()
File "odoo/http.py", line 1921, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2168, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 727, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/web/controllers/dataset.py", line 35, in call_kw
return call_kw(request.env[model], method, args, kwargs)
File "odoo/api.py", line 517, in call_kw
result = getattr(recs, name)(*args, **kwargs)
```
This is because of the recent refacre code with the commit [1]. method `_sendReceiptToCustomer` calls Python RPC where 4 arguments passed see [2], but the Python method was not dapted with chages of commit [1].
This commit fixes the above issue by setting `ticket_image` and `basic_image` as optional arguments and adapting the Python method according to these changes.
[1] - https://github.com/odoo/odoo/commit/47ec8957334aa37fd9b1d2267681fbd44064809f
[2] - https://github.com/odoo/odoo/blob/2eec78d10380893bd9dbfcef407de50c231cc3bb/addons/point_of_sale/static/src/app/screens/receipt_screen/receipt_screen.js#L111-L116
sentry-5662499209
Related ent PR- https://github.com/odoo/enterprise/pull/74145Scanning a package during an internal transfer now uses the package's actual stock location instead of the broader source location. This prevents validation errors when packages are stored in sublocations and makes barcode transfers more reliable.
Original PR description
### Before this PR: If you create new internal transfer with src location WH/Stock and than you scan a package that is on a sublocation of WH/Stock , the source location on the line is not set as the location of the package so when you validate in this situation an error pops because Odoo try to take the package from a different location of the package ### After this PR: The right location id is taken from the stock.quant and put on the line created
The Gantt view now handles cases where certain time scales, such as month or year, are not available but still selected. This prevents users from seeing a crash and keeps planning views usable with customized configurations.
Original PR description
The attribute scales of the gantt view specifies which scales are available in the view. This means that for instance "year" or "month" can be absent from scales. If that happens and that "year" or "month" is the selected range, a crash occurs when rendering the GanttRendererControls component:
TypeError: Cannot read properties of undefined (reading 'groupHeaderFormatter')
Here we assign to each range a function groupHeaderFormatter so that we can call it independently from the available scales.Users can now create loans with a 0% interest rate without running into an error during calculation. This helps accounting teams accurately record interest-free loans and avoids a blocker in the loan setup process.
Original PR description
Problem: Users are not allowed to set a zero interest rate on a loan. Steps to reproduce: 1. Go to accounting accounting > loans > new 2. Set any name and any amount in the borrowed field 3. Click on Calculate 4. Set interest rate to 0% and click Apply Explication: The library we were using "loanpy" does not handle the case where the interest rate is zero if the loan_type is `annuity`, and we ended up dividing zero by zero, throwing an error. The fix: If the interest is zero, we override the loan's type from `annuity` (the default) to `linear`, as the linear formula is better suited for the zero interest case. opw-4298272
Fixes an issue that caused an error when sending point-of-sale receipts to customers through WhatsApp. This restores the expected receipt sharing flow for cashiers and avoids failed customer communications after checkout.
Original PR description
Currently, an exception is generated when the user tries to send a POS order receipt on WhatsApp. error: ``` TypeError: PosOrder.action_sent_receipt_on_whatsapp() takes 3 positional arguments but 4…
Currently, an exception is generated when the user tries to send a POS order receipt on WhatsApp.
error:
```
TypeError: PosOrder.action_sent_receipt_on_whatsapp() takes 3 positional arguments but 4 were given
File "odoo/http.py", line 2363, in __call__
response = request._serve_db()
File "odoo/http.py", line 1891, in _serve_db
return self._transactioning(
File "odoo/http.py", line 1954, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 137, in retrying
result = func()
File "odoo/http.py", line 1921, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2168, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 727, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/web/controllers/dataset.py", line 35, in call_kw
return call_kw(request.env[model], method, args, kwargs)
File "odoo/api.py", line 517, in call_kw
result = getattr(recs, name)(*args, **kwargs)
```
This is because of the recent refacre code with the commit [1]. method `_sendReceiptToCustomer` calls Python RPC where 4 arguments passed see [2] but the method `action_sent_receipt_on_whatsapp` of `whatsapp_pos' is not dapted with chages of commit [1].
This commit will fix the above issue by adapting arguments when calling `action_sent_receipt_on_whatsapp`.
[1] - https://github.com/odoo/odoo/commit/47ec8957334aa37fd9b1d2267681fbd44064809f
[2] - https://github.com/odoo/odoo/blob/2eec78d10380893bd9dbfcef407de50c231cc3bb/addons/point_of_sale/static/src/app/screens/receipt_screen/receipt_screen.js#L111-L116
sentry-5662499209
Related community PR - https://github.com/odoo/odoo/pull/187829Miscellaneous changes
This commit reduces the number of read to a getter `editedRecord` which loops on all the record of the list to find the current one in edition. Forward-Port-Of: odoo/odoo#188596 Forward-Port-Of: odoo/odoo#188384
Original PR description
This commit reduces the number of read to a getter `editedRecord` which loops on all the record of the list to find the current one in edition. Forward-Port-Of: odoo/odoo#188596 Forward-Port-Of: odoo/odoo#188384
Steps to reproduce: - Go to a Website page. - Enable the "Mobile" preview. - Click on the "Edit" button to enter in edit mode. - Bug: When entering edit mode, the toolbar briefly appears and then disappears on the page. To fix this, we move the line that adds a "d-none" class to this toolbar earlier in the "start" of "snippetMenu". opw-4321865 opw-4232082 Forward-Port-Of: odoo/odoo#188353 Forward-Port-Of: odoo/odoo#188075
Original PR description
Steps to reproduce: - Go to a Website page. - Enable the "Mobile" preview. - Click on the "Edit" button to enter in edit mode. - Bug: When entering edit mode, the toolbar briefly appears and then disappears on the page. To fix this, we move the line that adds a "d-none" class to this toolbar earlier in the "start" of "snippetMenu". opw-4321865 opw-4232082 Forward-Port-Of: odoo/odoo#188353 Forward-Port-Of: odoo/odoo#188075
Updated the redirect URL from `/web` to `/odoo` to align with the new URL structure introduced. Forward-Port-Of: odoo/odoo#188553
Original PR description
Updated the redirect URL from `/web` to `/odoo` to align with the new URL structure introduced. Forward-Port-Of: odoo/odoo#188553
The issue: In the mobile view of the website page /profile/users, the ranking table's content overflows the screen. How to reproduce the issue: -Install the website_profile and website_slides_survey modules. -Go to the /profile/users page in the website view. -Switch to mobile view. Explanation: Table overflowed on smaller screens due to missing responsive wrapper. opw-4120453 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of
Original PR description
The issue: In the mobile view of the website page /profile/users, the ranking table's content overflows the screen. How to reproduce the issue: -Install the website_profile and website_slides_survey modules. -Go to the /profile/users page in the website view. -Switch to mobile view. Explanation: Table overflowed on smaller screens due to missing responsive wrapper. opw-4120453 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183291
Before this commit, the profile picture of a user would affect the dimensions of the image element. This commit fixes the issue by enforcing an aspect ratio of 1. Forward-Port-Of: odoo/odoo#188508 Forward-Port-Of: odoo/odoo#187830
Original PR description
Before this commit, the profile picture of a user would affect the dimensions of the image element. This commit fixes the issue by enforcing an aspect ratio of 1. Forward-Port-Of: odoo/odoo#188508 Forward-Port-Of: odoo/odoo#187830
Trying to upload a PDF, in some circumstances (e.g. multiple info due to pypdf being exported multiple times), would raise some warnings that were caught instead of being ignored. Forward-Port-Of: odoo/odoo#188108
Original PR description
Trying to upload a PDF, in some circumstances (e.g. multiple info due to pypdf being exported multiple times), would raise some warnings that were caught instead of being ignored. Forward-Port-Of: odoo/odoo#188108
Otherwise the patches remain in place, and it's possible for other modules to just assume things work if they happen to run after `test_website`. Forward-Port-Of: odoo/odoo#188608
Original PR description
Otherwise the patches remain in place, and it's possible for other modules to just assume things work if they happen to run after `test_website`. Forward-Port-Of: odoo/odoo#188608
Release notes: https://github.com/odoo/owl/releases/tag/v2.5.0 https://github.com/odoo/owl/releases/tag/v2.5.1 Forward-Port-Of: odoo/odoo#188406
Original PR description
Release notes: https://github.com/odoo/owl/releases/tag/v2.5.0 https://github.com/odoo/owl/releases/tag/v2.5.1 Forward-Port-Of: odoo/odoo#188406
Steps to reproduce: 1. Drag and drop a text snippet. 2. Select background video and insert the video in the mediaDialog. 3. Click on the add button. Issue: A traceback occurs due to the tag name not being found for an element. This issue was introduced in commit [1]. Issue link: https://github.com/odoo/odoo/issues/186874 Solution: This PR resolves the traceback by adding a `parentEl` condition in the replace media on save function. [1] : https://github.com/odoo/odoo/commit/36594d04a
Original PR description
Steps to reproduce: 1. Drag and drop a text snippet. 2. Select background video and insert the video in the mediaDialog. 3. Click on the add button. Issue: A traceback occurs due to the tag name not being found for an element. This issue was introduced in commit [1]. Issue link: https://github.com/odoo/odoo/issues/186874 Solution: This PR resolves the traceback by adding a `parentEl` condition in the replace media on save function. [1] : https://github.com/odoo/odoo/commit/36594d04a8909dd40ab6384f387c372ddae62345 Forward-Port-Of: odoo/odoo#188086 Forward-Port-Of: odoo/odoo#186876
Description of the issue/feature this PR addresses: - When working on this https://github.com/odoo/odoo/pull/186238 , few typos were discovered when populating data in demo database. - This pr fixes them - currently, the sample_ratio argument were not used in some methods [like this](https://github.com/odoo/odoo/blob/17.0/addons/mrp/populate/mrp.py#L363) instead values are hard coded. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forwa
Original PR description
Description of the issue/feature this PR addresses: - When working on this https://github.com/odoo/odoo/pull/186238 , few typos were discovered when populating data in demo database. - This pr fixes them - currently, the sample_ratio argument were not used in some methods [like this](https://github.com/odoo/odoo/blob/17.0/addons/mrp/populate/mrp.py#L363) instead values are hard coded. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187682
Since we moved away from activity_schedule in odoo/odoo#107804, the mail_activity_automation_skip context doesn't work anymore and activities get created regardless We add a check at the beginning of the function to make the context flag work again --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186898
Original PR description
Since we moved away from activity_schedule in odoo/odoo#107804, the mail_activity_automation_skip context doesn't work anymore and activities get created regardless We add a check at the beginning of the function to make the context flag work again --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186898
The previous code lead to cache-miss Courtesy of Dawn Hwang Forward-Port-Of: odoo/odoo#187772
Original PR description
The previous code lead to cache-miss Courtesy of Dawn Hwang Forward-Port-Of: odoo/odoo#187772
Steps to reproduce: - Create a product having the following attributes: - Color, which has `create_variant`: 'always' - Custom, which has `create_variant`: 'no_variant' - For each attribute, add a few values - Create a sale order for that product, using a combination of both attributes - Go to Inventory/Operation/Procurement/Replenishment - On the corresponding product, click on 'Order Once' - On the created Purchase Order, try to edit the product through the configurator Issue:
Original PR description
Steps to reproduce: - Create a product having the following attributes: - Color, which has `create_variant`: 'always' - Custom, which has `create_variant`: 'no_variant' - For each attribute, add a…
Steps to reproduce: - Create a product having the following attributes: - Color, which has `create_variant`: 'always' - Custom, which has `create_variant`: 'no_variant' - For each attribute, add a few values - Create a sale order for that product, using a combination of both attributes - Go to Inventory/Operation/Procurement/Replenishment - On the corresponding product, click on 'Order Once' - On the created Purchase Order, try to edit the product through the configurator Issue: A traceback will appear, as the generated matrix for this product will be a collection of pairs from [Color,Custom] values. But as the moves have no `product_no_variant_attribute_value_ids` to store that information, that part of the information will be lost and the generated orderpoint from which the PO is made will only be using an existing product.product. While this does not solve the issue, it at least allows to open the product configurator even though the line is faulty. Note: Same issue appear through a MTO flow, although in this case the product description will be correct. But trying to open the configurator would still lead to a traceback anyway. opw-4197302 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188031
In case the quantity of a purchase order line is negative the generated picking will be a delivery but not a return. Meaning validating this delivery will not update quantity received on the purchase order line. This commit makes sur the `to_refund` key on stock move impact the value of `qty_received` only if the stock move is actually a return. opw: 4259022 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -
Original PR description
In case the quantity of a purchase order line is negative the generated picking will be a delivery but not a return. Meaning validating this delivery will not update quantity received on the purchase order line. This commit makes sur the `to_refund` key on stock move impact the value of `qty_received` only if the stock move is actually a return. opw: 4259022 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#187946
In this commit https://github.com/odoo/odoo/pull/155339/commits/ca2d54a81ebb2611c14b0fc06784bd5d285856e3, in the task form, we changed the sol field to make it editable even when the user has no sale access. Trying to edit this field in such conditions produces an Access Error, so we revert this commit. task-4207245 related-https://github.com/odoo/odoo/pull/155339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188538 F
Original PR description
In this commit https://github.com/odoo/odoo/pull/155339/commits/ca2d54a81ebb2611c14b0fc06784bd5d285856e3, in the task form, we changed the sol field to make it editable even when the user has no sale access. Trying to edit this field in such conditions produces an Access Error, so we revert this commit. task-4207245 related-https://github.com/odoo/odoo/pull/155339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188538 Forward-Port-Of: odoo/odoo#182158
If we only use the community module, there is no interface to activate the automated stock accounting feature on the accounting page. Instead, we have to manually assign group_stock_accounting_automatic to each user. However, from PR odoo/odoo#133254, any setting changes will change all of the property_valuations to 'manual_periodic'. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187826
Original PR description
If we only use the community module, there is no interface to activate the automated stock accounting feature on the accounting page. Instead, we have to manually assign group_stock_accounting_automatic to each user. However, from PR odoo/odoo#133254, any setting changes will change all of the property_valuations to 'manual_periodic'. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187826
This commit reduces the number of read to a getter `editedRecord` which loops on all the record of the list to find the current one in edition. Forward-Port-Of: odoo/enterprise#74582 Forward-Port-Of: odoo/enterprise#74449
Original PR description
This commit reduces the number of read to a getter `editedRecord` which loops on all the record of the list to find the current one in edition. Forward-Port-Of: odoo/enterprise#74582 Forward-Port-Of: odoo/enterprise#74449
Steps to reproduce ------------------ 1. Change the parent of the "Projects" folder to put it in another folder. 2. Delete that folder. The "Projects" folder will be deleted, despite the constraint preventing it from being deleted. This is because when a relational field is set as `ondelete=cascade`, we don't call the `unlink` on the cascaded records and let the database handle it. Therefore, the constraint is not triggered. With this PR, we check not only the folder being deleted, bu
Original PR description
Steps to reproduce ------------------ 1. Change the parent of the "Projects" folder to put it in another folder. 2. Delete that folder. The "Projects" folder will be deleted, despite the constraint preventing it from being deleted. This is because when a relational field is set as `ondelete=cascade`, we don't call the `unlink` on the cascaded records and let the database handle it. Therefore, the constraint is not triggered. With this PR, we check not only the folder being deleted, but also its descendants. Task-4241631 Forward-Port-Of: odoo/enterprise#74263 Forward-Port-Of: odoo/enterprise#71468
…o studio Have a flow where active_ids is in the url and is used by the action itself (with a dynamic context key for example). Enter studio and reload. Before this commit, this flow crashed, because active_ids was not present. After this commit it doesn"t crash. opw-4296198 Forward-Port-Of: odoo/enterprise#74539 Forward-Port-Of: odoo/enterprise#74291
Original PR description
…o studio Have a flow where active_ids is in the url and is used by the action itself (with a dynamic context key for example). Enter studio and reload. Before this commit, this flow crashed, because active_ids was not present. After this commit it doesn"t crash. opw-4296198 Forward-Port-Of: odoo/enterprise#74539 Forward-Port-Of: odoo/enterprise#74291
Steps - install hr_work_entry_contract_enterprise - Payroll > Work Entries > Select "This year" filter - ** UncaughtPromiseError > OwlError ** Cause With the addition of variable time ranges in Gantt, a new `year` scale is selectable but is missing from the view. Change Add year scale. When clicking on a cell or clicking on the "New" button, the start and end date of the work entries to create will be the beginning and end of the month. opw-4321645 Forward-Port-Of: odoo/enterprise
Original PR description
Steps - install hr_work_entry_contract_enterprise - Payroll > Work Entries > Select "This year" filter - ** UncaughtPromiseError > OwlError ** Cause With the addition of variable time ranges in Gantt, a new `year` scale is selectable but is missing from the view. Change Add year scale. When clicking on a cell or clicking on the "New" button, the start and end date of the work entries to create will be the beginning and end of the month. opw-4321645 Forward-Port-Of: odoo/enterprise#73820
Update enterprise formatting override for MX addresses to be consistent with community, see PR: https://github.com/odoo/odoo/pull/186926 Forward-Port-Of: odoo/enterprise#74503
Original PR description
Update enterprise formatting override for MX addresses to be consistent with community, see PR: https://github.com/odoo/odoo/pull/186926 Forward-Port-Of: odoo/enterprise#74503