Friday, August 30, 2024
6 changes · master
Enhancements to existing features
Printed pages from key accounting screens now have a more polished and consistent layout when users print directly from the browser. This improves readability for journal items, reconciliation, and account reports, making printed financial information easier to review and share.
Original PR description
This PR enhances the visual output when users initiate a print action directly from their browser. The changes ensure a more polished and consistent appearance of printed documents, addressing visual…
This PR enhances the visual output when users initiate a print action directly from their browser. The changes ensure a more polished and consistent appearance of printed documents, addressing visual issues and improving overall readability. Affected views: - Journal Items - Reconciliation - Account Reports task-4143220 | Journal Items - Current Result | Journal Items - Expected result | |--------|--------| | | | | **Reconciliation - Current Result** | **Reconciliation - Expected result** | |  |  | | **Reports - Current result** | **Reports - Expected result** | |  | |
Planning screens now hide actions, filters, cost measures, and time-tracking details from users who do not have the right permissions. This prevents confusing access errors and gives each user a cleaner view based on their role.
Original PR description
* = planning_holidays, project_timesheet_forecast We did this for preventing unauthorized access errors. We hid the following button and filter for planning users: - Publish button - Publish & Send - 'Shifts in Conflict' filter - Edit - Delete We hid the following measures for non-HR users: - Allocated Hours Cost - Effective Hours Cost We hid the following stat button and fields for non-timesheet users: - Recorded stat button - Effective Hours field - Percentage Hours field - Remaining Time field task-3823274
Manufacturing users can now start or pause multiple work orders at once from the work order list view. This reduces repetitive clicks and helps teams manage production flow more efficiently.
Original PR description
Addition of a mass start/pause button in wo list view task-id: 4072809 Community: https://github.com/odoo/odoo/pull/174400
Project task scheduling now considers the availability of all assigned users, reducing planning conflicts for shared tasks. It also ignores outdated deadlines when recalculating schedules and lets users undo smart scheduling changes if the result is not suitable.
Original PR description
[IMP] project: {re,}schedule multi users tasks Before this commit: - {auto planning / moving forward and backward} tasks with multi users is following the company calendar leading to create…
[IMP] project: {re,}schedule multi users tasks
Before this commit:
- {auto planning / moving forward and backward} tasks with multi
users is following the company calendar leading to create conflicts.
- a bug was found, the first possible date to plan is taking into
account the deadlines of the tasks that will be planned. for example
if task A is blocking task B and the deadline of A is 01/05/2023,
first planned date to plan for B will be 01/05/2023
then if A was planned with a new deadline before the old one 01/04/2023
so the old deadline should no more impact task B planned_date_begin.
- It's not possible to undo the scheduling if the user is not satisfied
with the result.
After this commit:
- tasks are planned in a time that would be suitable for all users.
- old deadlines of tasks to plan are no more taken into account.
- An 'undo' button in a notification toast after a smart
scheduling in the project task gantt view has been triggered. This
allows the user to rollback to the previous state.
Technically,
for move back/for{ward}, kahn algorithm with priority queue was changes
to a simple for loop.
why ? before this commit, an index is stored and keep incrementing for
each interval. There is no need to iterate intervals again as we're
pretty sure that previous intervals are used and the coming ones are
not used
but in this commit, a user availabilities can be in his intervals and
in another interval for his availabilities and another user, so there is
no way to be sure that coming intervals are not used as they can be used
in another context.
keep in mind, that in case of perf problems, it's possible to implement
again kahn approche and verifying if the coming interval is good or not
by comparing it with the used for planning, it's a bit complicated to
implement and maintain. but it's still a possible optimized solution if needed.
task-3853065Approval rules in Odoo Studio can now support up to nine steps instead of three, making it easier to model more complex approval flows. The related field label has also been simplified to "Step" for clearer configuration.
Original PR description
This task adds more steps in the notification_order selection field of approval rules. It initially contained 3 steps, and has now 9. This allows more complex approval configurations. The field has also been renamed into "Step". A deeper refactoring of the feature will come after v18. Task~4122978
This update simplifies how the UrbanPiper point of sale integration identifies the current order. It reduces reliance on duplicate internal logic, helping keep order handling more consistent and easier to maintain.
Original PR description
Remove `selectedOrder` getter to use `get_order()` instead. taskId: 4141914