Friday, June 9, 2023
5 changes · master
Enhancements to existing features
The My Expenses status bar now includes company-paid expenses in the “to submit” and “under validation” counts, giving employees a more complete view of pending expense activity. The “to be reimbursed” count is limited to the relevant reimbursement items, making the status totals clearer and more accurate.
Original PR description
Before: in the "My Expenses" statusbar, only expenses paid by the employee were shown. Now: for the "to submit" and the "under validation" states, we show expenses paid by the employee AND the company. For the "to be reimburses" state, we ONLY show expenses paid by the company. task-3319115
Inventory lots and serial numbers can now include extra business properties, making it easier to distinguish items by quality, condition, or industry-specific attributes. Users also get improved lot views and search options, plus added visibility for locations, repairs, activities, and recent delivery partners.
Original PR description
Lots and serials are currently only differentiated by their number and potentially expiry dates. In many industries, they choose their lot/serial based on many data. For instance on Iron lots in the metal industry there are multiple properties helping to define the quality. This also happen in the second-hand industry and many others. added: - properties field on stock.lot - properties field on stock.quant, related to stock.lot - kanban view on stock.lot - search on properties in stock.lot and stock.quant list views task 3061173 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo adds a shared name lookup service that batches and caches display names, then uses it in spreadsheets. This should reduce repeated background requests and make spreadsheet-related screens load names more efficiently without changing user workflows.
Accounting reports now use a dedicated report setting to control when lines are grouped, instead of relying on a hidden configuration parameter. This makes the behavior easier to manage consistently across reports such as partner ledgers, aged balances, and asset reports.
Original PR description
Since these commits: - https://github.com/odoo/enterprise/commit/d6e771f1f9ab4440e47188ea24c2fc80f58c2919 - https://github.com/odoo/enterprise/commit/51bc88bdec323035c5d1949a8ab76e2c032b26f2 Several reports were using a config parameter to define a threshold used to group report lines. The goal here is to replace this parameter by a new `prefix_groups_threshold` field on `account.report`. task-3330099
Resolved issues and error corrections
Website headers now keep separate colors for the overlay and scrolled navigation states, including transparent and gradient backgrounds. This prevents unexpected color blending, giving website editors more predictable control over how the navbar looks before and after scrolling.
Original PR description
This commit allows to have really transparent navabars. Before this commit when the user put transparency on his header, it did not become transparent and the color was just mixed with white.…
This commit allows to have really transparent navabars. Before this commit when the user put transparency on his header, it did not become transparent and the color was just mixed with white. Moreover, this commit also allows to fix a bug a bit tricky: To simplify the explanation below, note that option "C" means the Colors option of the header (just below the Template option) and the option "BHP" means the background option below Header Position. By following these steps: - Drop some block in a the page (to be able to scroll) - Set a very transparent red as the value of C. - The navbar is now in a pinkish color. - Set the navbar position to "Over the content" - With the option BHP, set the background color to a dark color. => When you are at the top of the page, the color is the one of the option BHP. So far so good. Now when we scroll, the color of the navbar is dark red. This is not what the user expects. In this configuration, the C option should set the color of the navbar once the user has scrolled. The colors should not be mixed. Technical explanation of the problem: Option BHP applies the color on the header element and option C sets the color on the nav element. `NAV` element is a child of `HEADER` element. So when `HEADER` has a color set by BHP and nav has a color set by C which has transparency, the color of the `HEADER` influences the color of the navbar when scolling. This commit allows to correct this. task-2904507