Wednesday, December 6, 2023
10 changes · master
Enhancements to existing features
This update prevents users from logging or linking timesheets to down payment sales lines, helping avoid incorrect billing records. It also makes overrun tasks easier to spot by showing progress above 100% consistently in red across task views and reports.
Original PR description
Before this commit: - project.task form view > it makes no sense to timesheet on a down payment as this is not the service that was sold to the customer. - users are not alerted that there are no remaining hours on the task as the information can be a bit hidden under the timesheets notebook After this commit: - project.task form view > it's not possible to select an SOL linked to a down payment for projects, tasks, timesheets and tickets. - project.task form view > the progress is displayed in red if > 100%. task-3476795 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
List view columns now resize more predictably when users adjust their width. Instead of changing the overall table width, the adjustment is balanced with a neighboring column, making list views easier to work with and less visually disruptive.
Original PR description
Impacted Version: - 16.4 or above This commit improve below features: - Improve list view resizing behaviour Originally resizing list view column will result in whole table width change. With this update, the width change on one column will resize the sibling th element width instead. 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
Indian companies can now choose whether to enable the audit trail feature instead of having it applied automatically. This gives businesses more control over compliance settings at the company level while keeping the option available when needed.
Original PR description
Before This Commit: Currently, the Audit trail feature is applied to all Indian companies. After This Commit: The audit trail feature is optional now. it can be enabled in the company. Task - 3614528
Customer follow-up reports now exclude miscellaneous journal entries by default, since these entries often do not reflect a customer's actual payment status. Users can still choose to include them manually when needed, helping teams focus follow-up activity on the most relevant outstanding items.
Original PR description
Miscellaneous entries are very often not relevant to the client "status" internally. This commits excludes these entries from the follow-up report by default. They can still be included manually. task-3604569 enterprise PR: https://github.com/odoo/enterprise/pull/52101
Twitter/X social replies can include user mentions again after earlier restrictions were removed. The related anti-spam workaround and leftover cleanup code were removed, simplifying the Social and Twitter social integration while restoring expected reply behavior.
Original PR description
Purpose ======= In odoo/enterprise/pull/51752 , we remove the anti-spam system and we re-activated the mentions. This commit clean the methods / code that couldn't be removed in stable. Task-3615860
Follow-up reminders can now automatically add selected users as followers on the customer record when a configured follow-up step is run. This helps accountants and other responsible staff see replies in the customer chatter and avoid missing important payment-related responses.
Original PR description
Follow-up emails only appear in the partner chatter (since follow-ups are not their own dedicated model). The same holds for the (potential) reply of the partner to the email. If the accountant does not follow this chatter they may miss the reply. This commit adds a new option to the follow-up levels that allow adding users as followers of the partner chatter (when the follow-up level on which the option is set is executed). task-3604569 community PR: https://github.com/odoo/odoo/pull/144945
Grouped planning rows now use colors to show whether scheduled hours are below, matching, or above a resource’s available working time. This helps managers quickly spot underuse or overbooking while accounting for flexible hours, time off, and non-human resources.
Original PR description
In this commit, we add different colorings to the group rows (in the grouped gantt view) to indicate whether the planned hours are more (red), less (orange), or equal (green)to the resource's working hours for that day. task-3071699
Odoo Studio’s interface has been reorganized to reuse common visual components and remove duplicated or unused styling. This makes areas such as app creation, icon editing, sidebars, and search configuration more consistent and easier to maintain, with no major workflow changes expected for users.
Original PR description
Some css was not used anymore by components, and other styling rules were present in multiple locations, without using a consistent layout. Since the rewrite of Studio, the stylesheets were not modified and improved to match the component oriented paradigm. Scss mixins have been removed from the main 'mixins.scss' file. Some were not used, while others were only used once. Those rules have been moved directly to the desired stylesheet. This commit concerns mostly the App + Icon editors, the Sidebar and 'Add ... button hooks'. Many small other improvements can be seen in general in the studio app. The style should be more consistent accross similar elements, and inline css was moved to bootstrap classes as well. Tests affected by those changes have been adapted as well to match the latest classnames and remove some assertions no longer required since we now use less custom elements that could be replaced by components (e.g. Dropdown behaviors). task-3572251
This update makes time logging actions clearer, prevents users from recording timesheets against down payment sales lines, and improves guidance for field service invoicing. These changes reduce billing mistakes and make service-related workflows easier to understand.
Original PR description
Before this commit: - confirm time spent wizard: the implication of each button from the is not explicit. - it makes no sense to timesheet on a down payment as this is not the service that was sold to the customer. - the employee/SOL mapping tip is not accurate in field service as the behavior is a bit different there. After this commit: - confirm time spent wizard: buttons changed: save -> log time discard -> resume timer delete -> fa-trash icon 'discard' and 'delete' buttons are switched - it's not possible to select an SOL linked to a down payment for projects, tasks, timesheets, - project.project form view > invoicing notebook > the tip is different for fsm projects. task-3476795
When a spreadsheet is added to a dashboard, the original file in Documents is now automatically moved to trash. Users also receive a clear notification, reducing duplicate files and keeping Documents cleaner.
Original PR description
When the user clicks on "Add to dashboard", we should send the original spreadsheet to the trash in Documents and notify him that "The original spreadsheet has been sent to trash." TaskID: [3602669](https://www.odoo.com/web#id=3602669&cids=2&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)