Thursday, November 7, 2024
23 changes
5 changes
Resolved issues and error corrections
This fixes an issue in Odoo Studio exports where built-in system fields could be handled incorrectly. Exports should now use the proper field names, making exported data more reliable for users.
Original PR description
Use the name instead of the field instance.
This fix improves the wording of an error shown when users scan a barcode that is not found during receipt operations. It makes the message clearer and more professional, reducing confusion for warehouse staff.
Original PR description
Barcode --> Operations --> Receipts --> NEW Scan a barcode that doesn't exist in the DB ie: "5449000000996" The current error message's spelling and grammar are off. opw-4307102
Installing the Payroll Accounting module on a new database will now also install the required Accounting app. This prevents setup gaps and ensures payroll accounting features work as expected from the start.
Original PR description
When installing hr_payroll_account on an empty DB, we expect the Accounting app to be installed. But that is not the case. hr_payroll_account should depend on the accountant app.
The commission plan form now uses the standard date range selector, making start and end date selection work better on mobile devices. This reduces friction for users managing commission plans from phones or tablets.
Original PR description
before this commit, commission plan form date field selector seems broken in mobiles devices because we did not directly used widget available. after this commit, use daterange widget.
The sale commission plan list view no longer shows the status field twice. This removes duplicate information from the screen, making the list cleaner and easier for users to read.
Original PR description
in this PR, fixed an issue where the status of the sale commission plan was being displayed twice. This fix ensures that the status information is shown only once.
15 changes
Resolved issues and error corrections
Duplicating a project from the kanban view no longer keeps the original project's stage. New copies now start in the expected default stage, helping teams avoid misplaced projects and workflow confusion.
Original PR description
Steps to reproduce: - Settings > Enable 'Project Stages' - Projects app > New Project > Drag it into 'In Progress' stage - From Project Kanban view duplicate that project The duplicated project is created directly in 'In Progress' stage when it should have defaulted to the lowest sequence stage 'To Do'. Other duplication actions notably do not have this same issue. The kanban action specifically fetches default_stage_id from the context instead of using the dedicated default function of the sage_id field, but more generally we never want to copy the stage (as indicated by copy=False) so this fix covers for other possible mistakes. opw-4291455 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
3 changes
Resolved issues and error corrections
This update corrects broken links within the Helpdesk Team form view, ensuring users can easily access relevant documentation. The fix resolves inaccuracies in links to E-learning, Visibility, Email Alias, and Community Forum resources. This improves the user experience and facilitates proper Helpdesk setup and usage.
Original PR description
This PR corrects incorrect documentation links in the Helpdesk Team form view. Steps to reproduce: 1) Install the Helpdesk module. 2) Open any Helpdesk Team or create a new one. 3) Check the documentation links in the following sections: - E-learning - Visibility - Email Alias - Community Forum 4) Notice the incorrect or broken links. **Note**: We do not need to update the .pot file. task-4266660
This fixes an accounting test that was failing after a recent change in how journal entries are created. It helps keep payment discount behavior properly verified in the community edition, reducing the risk of regressions in accounting workflows.
Original PR description
The test_payments_epd_eligible_on_move_with_payment is no longer passing in community since this commit https://github.com/odoo/odoo/commit/0c2810df991b5ac48483f03d4cd0f5d281ece4b8. This is because a journal entry is now always generated in community edition, whether an outstanding account is provided or not. runbot issue: 105488 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Purchase order PDFs now show tax labels as clean text instead of displaying raw HTML tags. This makes printed purchase documents clearer and more professional for users, especially when using localized tax descriptions.
Original PR description
When printing the purchase order, the tax values were displayed with HTML tags because the field is an HTML field, and it was passed to the `join` function, which treated it as plain text. ```<span t-esc="', '.join(map(lambda x: x.description or x.name, line.taxes_id))"/>``` To fix this, the tax values are now converted to plain text before being passed to the `join` function. Steps to reproduce: 1. Create a purchase order PDF using taxes from a localization (e.g., Belgium). 2. Print the purchase order and observe the tax values displaying with HTML tags. opw-4260595 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects several documentation links that still sent users to version 17 pages. Users working with Point of Sale, Spanish localization, US accounting localization, and POS box setup will now be directed to the appropriate version 18.0 documentation.
Original PR description
* = point_of_sale, l10n_es, l10n_us_account, hw_posbox_homepage 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
Purchase order documents now display the tax name instead of the tax description. This prevents visible HTML tags from appearing in the Taxes column, making printed purchase orders clearer and more professional.
Original PR description
Version: 18.0+ Issue: Currently we are using the `description` of the tax to place on the report. This will cause the `<p>` tags to show on the report because `description` is a HTML field. Purpose of this PR: To only use the tax name to show on the purchase order document by changing to a list comprehension. Steps to reproduce on runbot: install purchase create an purchase order assign a tax print purchase order `<p>` tags will show under the Taxes column. Notes: In previous versions `invoice_label` was being used for this report. opw-4292687 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The translation button for text and character fields is now positioned within its field instead of floating over nearby data. This improves readability and usability in forms with related records, especially when editing translated content.
Original PR description
In x2many form field, the translation feature appears at the end of the row and hovers some data. This commit: 1. Fixes the issue by ensuring that the element is positioned relatively to its container (cf. the translatable field). 2. Refactors the css related to the char_field and text_field translation buttons to avoid negative margins but also to simplify the css. task-4273364 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes and improves Hoot, Odoo’s internal browser-based testing framework, along with related unit tests across several apps. It makes test reporting clearer, reduces stale failed-test results, improves mocked browser behavior, and helps developers catch issues more reliably before they affect users.
Original PR description
## Pull Request HOOT (PRHOOT) - part 26 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PRHOOT) - part 26 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Part 16: https://github.com/odoo/odoo/pull/166311 Part 17: https://github.com/odoo/odoo/pull/168328 Part 18: https://github.com/odoo/odoo/pull/171004 / https://github.com/odoo/enterprise/pull/65657 Part 19: https://github.com/odoo/odoo/pull/171242 / https://github.com/odoo/enterprise/pull/65767 Part 20: https://github.com/odoo/odoo/pull/173332 / https://github.com/odoo/enterprise/pull/66895 Part 21: https://github.com/odoo/odoo/pull/174337 Part 22: https://github.com/odoo/odoo/pull/176777 / https://github.com/odoo/enterprise/pull/68721 Part 23: https://github.com/odoo/odoo/pull/179660 / https://github.com/odoo/enterprise/pull/69728 Part 24: https://github.com/odoo/odoo/pull/181971 Part 25: https://github.com/odoo/odoo/pull/183358 Enterprise: https://github.com/odoo/enterprise/pull/73361 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The invoice portal now handles invoices without a due date without crashing. This prevents customers from seeing an error when opening their invoice list and keeps portal access reliable even when payment due dates are left blank.
Original PR description
Currently, an error occurs when opening a portal view of invoices and any invoice has no 'Due Date' Step to produce: - Install the ```account``` module. - Create a new invoice, add a customer name…
Currently, an error occurs when opening a portal view of invoices and any invoice has no 'Due Date' Step to produce: - Install the ```account``` module. - Create a new invoice, add a customer name and an invoice line, then save the record. - After that, remove the 'Payment terms' and confirm the invoice. - Then Remove a 'Due Date' and save a record. - Go to portal view and try to open 'Your Invoices', ```TypeError: '<' not supported between instances of 'bool' and 'datetime.date'``` An error occurs when the system tries to compare an invoice's due date with today's date at [1], but the due date is missing. Link [1]: https://github.com/odoo/odoo/blob/1615bdb7e52e5ad501922568a1baaee4fd07a4b7/addons/account/views/account_portal_templates.xml#L72 To resolve this issue, add a condition to skip the comparison between the invoice's due date and today's date, if the due date of invoice is unavailable. Sentry-6016842018 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where users could not properly use the attachment popout from accounting move lines after a related mail service change. It restores the expected workflow for viewing attachments without disrupting accounting tasks.
Original PR description
Before this commit, the attachment_view_move_line component was not adapted to the new changes done in the mail_popout_service. This commit solves this problem. task-4275364
Warning messages shown during shift swaps, time off conflicts, and shift conflicts now take up less unnecessary space. This makes the planning screen easier to read and reduces visual clutter for managers and employees.
Original PR description
Prior to this commit, the alert displayed in planning for shifts-switch, time off conflict and shifts conflict was too big, leaving a lot of empty space within the div. This commit sets some bootstrap classes to fix the issue. Task: 4224786
This fixes an error in recruitment document processing caused by using the wrong candidate reference. It also improves skill detection so skills are recognized when they appear at the very start or end of a text, making extracted candidate information more reliable.
Original PR description
Traceback due to typo: applicant_id -> candidate_id \+ fix regexp to also match skills at the start and end of the text \+ make tests fail without the fix task-4207776
This fixes an automated Web Studio test so it checks approval behavior on apps that are already installed, matching the real upgrade workflow. It helps ensure approval rules are properly validated when users upgrade installed apps, without changing day-to-day functionality.
Original PR description
The trigger in the tour that filter apps was wrongly set to "Not Installed", instead of "Installed". Indeed, that tour puts approval on ir.module's updgrade button, so on already installed apps, and check whether approval rules are triggered when clicking on the "upgrade" button. So we need to filter only installed apps in the ir.module kanban.
Users can no longer drag documents while viewing the Trash folder. This prevents errors and confusing notifications by clearly explaining why the action is not allowed.
Original PR description
**Before this PR:** Dragging and dropping documents from the TRASH to another folder will result in a traceback or user error. Dragging and dropping documents within the TRASH will trigger an unusual notification. **After this PR:** Disable dragging in the TRASH folder and inform the user with a valid reason. Task-4231709
This fixes an automated walkthrough used to verify field service report behavior by removing unnecessary click actions from check-only steps. The change helps keep internal validation reliable without changing day-to-day user functionality.
Original PR description
In this commit, we remove useless run: "click" on steps that are just a check.
Dragging a folder to the trash now refreshes the Documents side panel correctly, so the removed folder disappears immediately. This prevents confusion by keeping the folder list in sync with the user's action without extra manual refreshes.
Original PR description
Purpose ======= Fix the left panel which wasn't updated when dragging a folder to trash. Specification ============= When dragging a document of type 'folder' to the trash, the model is correctly being notified but the search model isn't, the folder is thus still visible in the left panel. Fixing that by also reloading the search model when archiving a document. Moving the reloading methods calls from toggleArchive to onDropDocuments as it is the only method where we don't reload the model and search model after archiving. Keeping the reload calls in toggleArchive caused redundant reloads of the models. Task-4260645
This update resolves a test failure in the Amazon integration (sale_amazon) caused by a dependency on data that isn't available in the no-demo testing environment. The fix ensures that tests run correctly without relying on this unavailable data, maintaining the stability of the integration.
Original PR description
test_sync_pickings depends on street value, which does not exist in no-demo mode, thus breaking tests. This commit fixes the issue. [broken test](https://runbot.odoo.com/web#id=73283&view_type=form&model=runbot.build.error&menu_id=405&cids=1)
This update fixes an issue where the app logo wasn't immediately updated after a user changed its icon or image. Now, the logo updates dynamically when a user confirms the change, providing a more consistent and user-friendly experience. This ensures users always see the correct branding.
Original PR description
Before this commit: The logo is not updated when users change the icon or image and click the confirm button. The updated logo appears after refreshing the page. After this commit: When users change the icon or image and click the confirm button, the logo is now updated Task-4219545