Tuesday, June 11, 2024
5 changes · saas-17.3
Resolved issues and error corrections
Fixed an issue where adding the Missing Skills column to the job applications list could cause repeated error pop-ups. Recruitment users can now view applications with this field enabled without interruptions.
Original PR description
In job applications view, if you add missing skills through studio, the fields computation throws an error
Steps to reproduce:
1.go to recruitment > applications > all applications > tree view
2.in studio > add missing skills field
3.the column will be added but an error on missing skill compute will appear
4.everytime you enter a "applications" tree view, an error will pop up for missing skill computation
Cause:
missing skill fields was not set during compute
Solution:
set missing skill during computeThis fixes an issue where enabling or disabling a payment provider showed the wrong published status after saving. Businesses can now trust that the payment provider status displayed in the admin matches whether it is actually available on the website.
Original PR description
Steps to reproduce ================== - Website > Configuration > Payment Providers - Enable a payment provider, and it will be published by default - Save your changes - Observed behavior: the…
Steps to reproduce ================== - Website > Configuration > Payment Providers - Enable a payment provider, and it will be published by default - Save your changes - Observed behavior: the status of the payment provider is Unpublished, even - though it is published on the website - When disabling the payment provider, the status will be changes to Published - If you try to unpublish it, you'll get the message You cannot publish a disabled provider - Expected behavior: it should be automatically published when enabled, and - automatically unpublished when disabled. At the moment, the behavior from the - front-end is okay, but the status of the publish button is wrong. Cause of the issue ================== Changes applied to readonly fields are not saved https://github.com/odoo/odoo/blob/4f325ef620263c27e095eb49026a677ac617a0ee/addons/web/static/src/model/relational_model/record.js#L623-L630 Since https://github.com/odoo/odoo/pull/137031 , the field has been removed from the view. It is now considered readonly. Solution ======== Add the field back to the view opw-3908473
This fixes an issue where spreadsheet chart names could show incorrectly after a recent chart settings change. Users will see the intended chart title in Odoo graph data, making spreadsheets easier to read and manage.
Original PR description
Since the recent chart options refactoring, the title of the chart is not longer a string but an object with different style-related keys and the title string is set in the key `text`. The getter `getOdooChartDIsplayName` was not adapted to this change. task-3978637 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
Fixes a visual issue on invoices where clicking into the product field made its text sit slightly lower than the other line items. This keeps invoice entry looking consistent and avoids distracting layout shifts while users edit product lines.
Original PR description
Description of the issue this commit addresses: When on on invoice, focusing in on the product cell slightly lowers the text on the line, this means that the text is not aligned with other cells anymore. This is not wanted. --- Steps to reproduce: 1-Install account 2-Open a new invoice 3-Add a product on a line 4-Focus in the cell of the product 5-Text is slightly lower than in other cells --- Desired behavior after this commit is merged: The text of the product cell is aligned with other cells --- Note on the fix: The bug happened because the buttons on the line were slightly taller than the text box. They are hidden when the focus is out the box so it would only be a problem when focusing in. The fix consists in making sure that the buttons are not taller than the text so they will not mess with the line height --- no task-feedback --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures chart names in Documents spreadsheets are read correctly after a recent change to how chart titles are stored. Business users should see the expected chart labels in menus and side panels, reducing confusion when working with spreadsheet graphs.
Original PR description
Since the recent chart options refactoring, the title of the chart is not longer a string but an object with different style-related keys and the title string is set in the key `text`. The getter `getOdooChartDIsplayName` was not adapted to this change. This commit adapts the tests in Enterprise. task-3978637