Daily updates from Odoo
Thursday, April 11, 2024
7 changes
1 change
Resolved issues and error corrections
Preparation displays now show order items in the intended sequence when a database starts. This helps kitchen or preparation teams read tickets consistently and avoid confusion caused by items appearing out of order.
Original PR description
Make the sequence ordered works in preparation display when starting a db task id : 3851247
6 changes
Resolved issues and error corrections
This fix corrects mismatched parameter names in the Luxembourg payroll system that resulted from two parallel updates. The names are now consistent across different software versions, ensuring the payroll system works correctly without requiring any database updates.
Original PR description
In https://github.com/odoo/enterprise/pull/57515 some parameter rules were added. It was master version and landed in saas-17.2 We needed the same parameter rules in 17.0 and 17.1 Thus, we made another PR - https://github.com/odoo/enterprise/pull/58163 Unfortunately, those two PRs were done somewhat parallely and some of the xml ids don't match. This commit fixes that. And as the https://github.com/odoo/enterprise/pull/58163 has not been deployed yet, we will not need upgrade script, as the changes has not reached to dbs yet.
This update resolves an issue where unnecessary scrollbars were appearing in the document inspector when document names or field values were too long. The fix adjusts how the inspector calculates available space for displaying information, ensuring content fits properly without requiring users to scroll horizontally or vertically.
Original PR description
Purpose ======= Fix the unnecessary horizontal and vertical scrollbars appearing in the inspector when a document name is too long. Specifications ============== In the inspector, when the value of the fields of type model (like the Journal Entry or Signature fields) is too long, the value is styled so that its width takes the max-width. However the field max-width is incorrectly computed. It is missing the table-sm class horizontal padding. The field is thus too big to fit in the inspector and scrollbars appear. Taking into account the table-sm paddings while computing the field value max-width. As the field label left padding is set to 0, the table-sm padding is multiplied by 3 (right padding of label, left and right padding of value). Also adding the "overflow-hidden" class on the inspector so that scrollbars never appear. Task-3829716 Forward-Port-Of: odoo/enterprise#60430 Forward-Port-Of: odoo/enterprise#59652
This update corrects how emoji icons are styled in Knowledge articles. Previously, a generic styling rule was accidentally making emoji icons in embedded views (like kanban cards) appear too large. The fix uses a more specific styling rule that only applies to the main article emoji, ensuring embedded emojis display at the correct size.
Original PR description
To stylish the main emoji of the article, we used the CSS selector `.o_field_knowledge_icon`. However, this selector is too generic and will match with other emoji fields present in the embedded views (see: `knowledge_icon` field). Example: In 17.0, we re-used the emoji field in the embedded kanban views of article items. With the selector `o_field_knowledge_icon`, those emojis will be as big as the main emoji, which is not what we want. To ensure that the CSS rules only applies to the main emoji of the article, we will instead use the selector `o_knowledge_icon`, which is specific to the main emoji of the article. Related: https://github.com/odoo/enterprise/pull/54522 task-3784013 Forward-Port-Of: odoo/enterprise#59885
The 'create stage' button has been removed from the project task kanban view because project users don't have the ability to create task stages. This change simplifies the interface by removing a non-functional option that was confusing users.
Original PR description
Due to the project user's inability to create a task stage, we have removed the 'create stage' option from the kanban view. task-3511164 Forward-Port-Of: odoo/odoo#140297
This update fixes the excessive spacing between quantity and unit of measure fields in the project milestone form view. The adjustment improves the overall layout appearance and provides a better user experience when viewing and editing project milestones.
Original PR description
Steps to reproduce: - Open the 'project.milestone' form view. Issue: - Excessive space exists between quantity and unit of measure in the 'project.milestone' form view, impacting the layout. Solution: - Reduce the space between elements to improve the layout and enhance the user experience. task: 3549267 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#139806
This update fixes a test in the base module that was failing when certain timezone data files were missing from the operating system. The change makes the test more resilient to different timezone package versions, preventing unnecessary test failures in environments where specific timezone targets aren't available.
Original PR description
See https://github.com/odoo/odoo/pull/151989#issuecomment-2041952639 The test test_tz_legacy will fail if the taget does not exist on the operating system. This is breaking in some versions of the tz-data package. Don't make this test fail if the target is missing. Forward-Port-Of: odoo/odoo#160868