Daily updates from Odoo
Monday, July 29, 2024
8 changes · master
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
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