Monday, July 29, 2024
19 changes
2 changes
Resolved issues and error corrections
Fixed an issue where opening certain partner links in a new browser tab could show the record the user was already viewing instead of the intended linked partner. This ensures duplicate Tax ID links and similar record links take users to the correct destination, reducing confusion and navigation errors.
Original PR description
Currently, links created with the `Many2OneField` component won't work properly if opened in a new tab. ### Steps to reproduce * create two partners with the same Tax ID * each partner should display a link to the other partner, indicating a duplicate Tax ID. * open one of those links in a new tab When the link is opened in a new tab, it displays the record you were originally viewing instead of the intended partner. opw-4050312
This update fixes several issues affecting everyday Odoo workflows, including loyalty orders, vendor bill purchase order selection, email sender handling, manufacturing work orders, and localized accounting reports. It improves reliability and compliance behavior across point of sale, purchasing, email, manufacturing, and country-specific accounting features.
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
8 changes
Enhancements to existing features
Restaurant table references now use a numeric table number instead of a free-text name across appointment, preparation display, and self-order preparation flows. This makes table identification more consistent for staff and customer-facing order preparation screens.
Original PR description
pos*: pos_restaurant_appointment, pos_restaurant_preparation_display, pos_self_order_preparation_display In this commit, we adapt the data model of the restaurant table. Its name becomes a table number: the field is changed from 'name::string' to 'table_number::integer'. Community PR: odoo/odoo#173108
9 changes
Enhancements to existing features
This update improves the error messages shown to users in Argentina when the electronic billing service (AFIP) is temporarily unavailable. Instead of asking users to contact their Odoo provider for a service issue they cannot fix, the system now provides clear guidance to wait and retry, making the user experience more helpful and accurate.
Original PR description
Gantt views now handle end dates more consistently by avoiding rounding to the last second of the day. This improves scheduling accuracy in planning, field service, projects, and other Gantt-based workflows.
Original PR description
*web_gantt, planning, industry_fsm
Before this commit:
- The default value of the end time in Gantt view was 23:59:59.
After this commit:
- The end time in the Gantt view will now default to 00:00:00 with one day/hr
ahead.
- Introduced a new parameter `roundUpStop` in the `getColumnStartStop` function.
- When this parameter is set to true, the default time for the end date
will increment by 1ms.
- When set to false, the end time remain as it is.
Task-3871980The expense onboarding flow now lets users either try a sample receipt or upload their own receipt. This makes the setup experience more realistic, while ensuring uploads are only available when the customer has data extraction credits.
Original PR description
Before this commit, the expense onboarding wizard offered the user 4 sample receipts to choose from. Now, the user can choose either a sample receipt, or to upload their own receipt. However, in order to upload their own receipt, they need to have credit for data extraction. A depiction of the updated user journey could be found here: https://link.excalidraw.com/l/65VNwvy7c4X/3RaHoyA4PFQ task-3901510
Users can now open the full project or task form from Gantt and Calendar views using the expand button. This makes collaboration details such as the chatter accessible without leaving the planning workflow.
Original PR description
Currently, when user open a task or project in the calendar or Gantt view, they cannot access the chatter. With this commit, they can now access the form view through the expanded button. Task: 3837229
Indian payroll now supports sandwich leave calculations, where intervening weekends or public holidays can be counted when leave is taken on both sides. This helps businesses apply local leave policies more consistently and deduct the correct number of leave days from employee balances.
Original PR description
This commit, adds the Sandwich Leave Rule in Indian Localization. The sandwich leave rule will be applied if an Employee takes leave like in the scenario below. Scene 1: Friday (leave) -> Saturday -> Sunday -> Monday(Leave) 4 Leaves will be deducted from the Employee's leave balance. Scene 2: Tuesday(Leave) -> Wednesday(Public Holiday) -> Thursday (Leave) 3 Leaves will be deducted from the Employee's leave balance. task-3950973
Event website sub-pages can now keep their own SEO titles and descriptions instead of unintentionally sharing the same values. This helps event organizers tailor search visibility and social previews for pages like talks and exhibitors independently.
Original PR description
**How to reproduce:** - Create an event and activate the submenu - Open Talk Proposal page and set specific SEO discription and title - Open Exhibitors page and set another one **Specifications:** - They are currently synced. - All the sub-pages except 'Introduction' and 'Location' page are synced. - SEO data of all the pages should be different from one another. **After this PR:** SEO data for all sub-pages will be different. Task-3874050
Global invoices for Mexican POS sales now use the POS reference, making the related ticket numbers visible on the invoice. This helps businesses provide clearer records during government tax audits and makes it easier to match invoices with sold tickets.
Original PR description
When there is a tax audit from the government, its common to check global invoices as they declare which tickets were sold during a certain period. This is not possible because the global invoice does not contain ticket numbers, it contains references which are only visible from Odoo and can be an issue for checking. [Ticket](https://www.odoo.com/odoo/project/4216/tasks/4061845?cids=17)
Resolved issues and error corrections
Removing HMRC authentication credentials now affects the user selected by the administrator, not the currently logged-in user. This prevents accidental removal of another user's UK tax reporting credentials and makes multi-user credential management more reliable.
Original PR description
This commit fixes the following issue and also improves the way the code is handling write/clean hrmc tokens on user. In the write/clear functions, `user` argument is now mandatory so that we can do…
This commit fixes the following issue and also improves the way the code is handling write/clean hrmc tokens on user. In the write/clear functions, `user` argument is now mandatory so that we can do the operation on the selected user rather than the environment user. Issue: Step to reproduce: - install`l10n_uk_reports` - create 2 user or more - for each user, fill their hmrc token values - select a user different from the current environment user - remove their credential with the button "Remove Authentication Credentials" Current behavior: - The selected user's credential is not removed, but the environment user one got removed Expected behavior: - the selected user's credential should be the one that is removed, and the environment user should not be removed. Why it happens: - In `_clean_tokens` function, it clears the credential of the environment user by default. Solution: - change the signature of _clean_tokens function to have `user` required argument and clean that user's token instead of `env.user` opw-4041604
Steps to reproduce: 1) Go to runbot Odoo 16 enterprise and install "l10n_ar_edi" module (Argentinean Electronic Invoicing). 2) Take position on Argentinian company (AR) (Responsable Inscripto) . 3)…
Steps to reproduce: 1) Go to runbot Odoo 16 enterprise and install "l10n_ar_edi" module (Argentinean Electronic Invoicing). 2) Take position on Argentinian company (AR) (Responsable Inscripto) . 3) Create customer electronic invoice and confirm. If there is a response with 503 error (HTTPError: 503 Server Error. Service Unavailable) while connecting to the webservice then it will be raised the error message and this text "Please report this error to your Odoo provider" (but this text is not suitable because the odoo provider can`t solve the error. The webservice is not available). Current behavior: If there is a response with 503 error (HTTPError: 503 Server Error. Service Unavailable) while connecting to the webservice when the user is trying to confirm an electronic customer invoice then it will be raised the error message and this text "Please report this error to your Odoo provider". Expected behavior: If there is a response with 503 error (HTTPError: 503 Server Error. Service Unavailable) while connecting to the webservice when the user is trying to confirm an electronic customer invoice then it will be raised the error message and this text 'The AFIP electronic billing webservice is not available. Wait a few minutes for it to reset and try to validate the action again.'. Task Adhoc: 37771 Forward-Port-Of: odoo/enterprise#59983
This update adds customer contact information to the receipt header for Chilean Point of Sale invoices (facturas). This change ensures compliance with Chilean tax and legal requirements for invoice documentation. Customers will now see complete contact details on their receipts.
Original PR description
In this commit, we had the partner information to the receipt header of the CL PoS when the order is a factura. This is needed in order to be compliant with the CL law. task-id: 3747828
This release includes several improvements and fixes across multiple Odoo Enterprise modules. Key updates include performance optimizations in the report editor, enhancements to salary attachment views, improvements to gantt view loading, fixes for sign document resizing, and new document layout options. These changes improve system performance, user experience, and functionality across accounting, HR, project management, and document signing features.
Resolved issues and error corrections
Fixed an issue where VAT Record Books exported from Spanish tax reports were displaying numbers as text instead of actual numbers. This fix allows users to perform calculations and operations directly on the exported spreadsheets, improving usability and reducing manual data conversion work.
Original PR description
With an ES Company Open Tax Report Select Report > Generic Tax Report Export "VAT Record Books" Issue: Numbers are exported as string, while the system should export as number, to let users execute operations on the resulting workbook opw-4029478
Users can now successfully move documents to parent workspaces. Previously, a technical issue prevented this action from working correctly. This fix resolves the underlying problem so users have full flexibility in organizing their documents across workspace hierarchies.
Original PR description
Before this fix, one couldn't move documents to the parents workspaces. This was due to a check on the 'active' class of the target's child elements and not only on his direct descendant. This commit fix this by adding ':scope > ' to the selector. Task-3999790 Forward-Port-Of: odoo/enterprise#65000
This fix resolves a problem where users couldn't navigate away from locked or read-only articles. When switching between articles, the system was attempting to rename read-only articles, which failed and prevented users from leaving. The fix prevents these unnecessary rename attempts for articles users don't have permission to edit.
Original PR description
This commit fixes an issue with locked/readonly empty articles. If a user opens an article which is locked/readonly for them, when switching articles the browser will try to update the article's name. This operation is of course not possible, but this leads to the user not able to leave said article. This is caused by the update method on the record which sets it as dirty so that it can be saved when possible. In order to fix, this when the user has no write access on the article or if it is locked, we return early so that the record doesn't set itself as dirty. task-4047722
Fixed a bug in the Follow-up Reports feature where the Save button would not work after changing the "Exclude from Follow-up" field. The field was automatically saving changes, leaving nothing for the Save button to process. This fix disables auto-save for this field, restoring normal save functionality and matching the behavior in other Odoo versions.
Original PR description
This bug is only present in v17.0.
### Steps to reproduce:
- Go in Accounting > Customers > Follow-up Reports
- Click on a customer
- Changing the "Exclude from Follow-up" field of a line
- The save button does not work anymore
### Cause:
The field "Exclude from Follow-up" is in autosave by default. So it is saved every time it is changed. When clicking on the save button there is nothing to save so nothing happens and the button stays there.
### Solution:
Add `options={'autosave': False}` in the field to prevent it from saving. This will create the same behavior as in all other versions.
This bug does not appear in 17.1 because a new condition called canSaveOnUpdate is added: https://github.com/odoo/odoo/blob/2db71d627fd2c9fc97d573df7993a953753bb8bd/addons/web/static/src/model/relational_model/record.js#L256
opw-4055350The GST Return Period filter has been updated to display both the current and previous month or quarter by default, instead of only showing the previous period. This change makes it easier for users to access and work with the most relevant GST return periods without having to manually adjust filters.
Original PR description
Before this **PR**: The default filter for the GST Return Period shows the previous month or quarter. After this **PR**: The default filter for the GST Return Period shows the current as well as the previous month or quarter. **task**-4014267
This fix corrects how state information is submitted in Brazilian electronic invoices. Previously, the system was sending state names instead of state codes, which caused some states like Minas Gerais to reject invoices. Now the correct state codes are sent according to the official specification, ensuring invoices are accepted by all Brazilian states.
Original PR description
It turns out we've been sending the wrong value in the state field [1]. This hasn't caused issues for the majority of states, but some states reject invoices if they don't have the right code (e.g. Minas Gerais). opw-4076445 [1] The specification mentions state *code*: https://avataxbr-docs.avalarabrasil.com.br/#/Invoice%20Goods/sendInvoiceGoods