Friday, September 20, 2024
18 changes · master
Enhancements to existing features
The employee referral dashboards were updated to use newer, simpler card layouts and standard styling. This makes the referral screens easier to maintain and helps keep the user experience consistent with current Odoo interface standards.
Original PR description
In this commit we have simplified the kanban arch for the hr_referral module dashboard. the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
This change updates an internal Studio test to match a recent enhancement that lets character fields handle placeholder text. It helps keep automated quality checks aligned with the product behavior, reducing the risk of false test failures during development.
Original PR description
In this commit: https://github.com/odoo/odoo/commit/fca4ad09d929ceee8820fc8b23ab7edd0898639c we added a new props to the char Field. So this test need to be adapted. task: 4191835 Community pr: https://github.com/odoo/odoo/pull/180744
The room booking app now uses the shared loading screen styling instead of maintaining its own duplicate styling. This reduces maintenance effort and helps keep the user experience consistent across Odoo, with no expected functional change for users.
Original PR description
- The room app was using his own CSS for the blocked UI. Indeed, it used the service but its CSS was not available. It now is, instead of more CSS code to support. - The web_enterprise app is using a div using the o_blockUI class... but this seems like a mistake, it never had an effect (since at least version 16.0). To investigate later. Related to task-4184418
Several kanban views were simplified so cards are easier to maintain and align with current Odoo interface standards. Users should see the same workflows with more consistent card behavior and presentation across inventory, manufacturing, Studio, and WhatsApp areas.
Original PR description
*stock_barcode_mrp,stock_barcode_picking_batch,test_web_studio In this commit we have simplified the kanban arch for the planning, project_forecast,quality_control,room,sale_subscription and sale_timesheet_enterprise modules.the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name="..." widget="image"/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color="color_field_name" on root node Task-3992107
The Plan Services field now has clearer tooltip text explaining how it affects automatic planning. This helps users understand when services will be automatically planned and reduces confusion during product setup.
Original PR description
This commit simply adds help text to the tooltip of the field 'plan services' (`planning_enabled`). We add the explanation about how the behavior of 'auto plan' is linked to this field. Task: 3940616
The GST return dashboard layout for India reports has been simplified to use newer interface components and clearer labels. This makes the dashboard easier to maintain and helps users see a more accurate status label for waiting reception.
Original PR description
In this commit, we have simplified the Kanban arch for the l10n_in_reports_gstr module dashboard. the goal is to simplify them, make them easier to read, and use bootstrap utility class names. -…
In this commit, we have simplified the Kanban arch for the l10n_in_reports_gstr module dashboard. the goal is to simplify them, make them easier to read, and use bootstrap utility class names. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of <field/> tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use <field name=... widget=image/> instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node also, change 'Waiting for Status' to 'Waiting Reception' as it is not available in gstr2b_status https://github.com/odoo/enterprise/blob/8819f2d2145577cac800a2e149b287ae88000336/l10n_in_reports_gstr/views/gst_return_period.xml#L275 Task-3992107
Miscellaneous changes
payment_method_id is readonly in account.batch.payment's form view when there is at least one payment on the batch. So, it cannot easily be changed in standard in order to break the constraint. It could however happen in custom views or when generating records directly from the code. Forward-Port-Of: odoo/enterprise#70230
Original PR description
payment_method_id is readonly in account.batch.payment's form view when there is at least one payment on the batch. So, it cannot easily be changed in standard in order to break the constraint. It could however happen in custom views or when generating records directly from the code. Forward-Port-Of: odoo/enterprise#70230
before this commit, when opening/resuming a POS session, the final_consumer was not always loaded, leading to loading errors. This commit ensures that the final_consumer gets loaded when opening the POS session. related PR: https://github.com/odoo/enterprise/pull/65296 opw-4171779 Forward-Port-Of: odoo/enterprise#70251
Original PR description
before this commit, when opening/resuming a POS session, the final_consumer was not always loaded, leading to loading errors. This commit ensures that the final_consumer gets loaded when opening the POS session. related PR: https://github.com/odoo/enterprise/pull/65296 opw-4171779 Forward-Port-Of: odoo/enterprise#70251
### Steps to reproduce * install `account_intrastat` * create and confirm an invoice for a Northern Irish customer * open the EC Sales Report You will see that your invoice is not included in the report opw-4123375 Forward-Port-Of: odoo/enterprise#69955 Forward-Port-Of: odoo/enterprise#69501
Original PR description
### Steps to reproduce * install `account_intrastat` * create and confirm an invoice for a Northern Irish customer * open the EC Sales Report You will see that your invoice is not included in the report opw-4123375 Forward-Port-Of: odoo/enterprise#69955 Forward-Port-Of: odoo/enterprise#69501
Before this commit, it was not possible to resequence the projects in any list views of Project and Field Service because the `handle` widget is not defined in the sequence and the default order applied in those list views does not begin with `sequence` field. This commit shows the sequence field in the list view of `Field Service > Configuration > Projects` and change the default of that list view to allow the user to resequence the projects as he wishes. Community PR: odoo/odoo#180403
Original PR description
Before this commit, it was not possible to resequence the projects in any list views of Project and Field Service because the `handle` widget is not defined in the sequence and the default order applied in those list views does not begin with `sequence` field. This commit shows the sequence field in the list view of `Field Service > Configuration > Projects` and change the default of that list view to allow the user to resequence the projects as he wishes. Community PR: odoo/odoo#180403 Close odoo/odoo#176961 Forward-Port-Of: odoo/enterprise#70137
The `Accounting` dashboard was using very naive formulas to compute deltas between years. Namely, the formulas were based on the assumpution that we'd only compare values year by year but the filters allow to work with quarters or months as well. This revision updates the dashboard file to take the months/quarters into account. task-3957037 Forward-Port-Of: odoo/enterprise#70255 Forward-Port-Of: odoo/enterprise#69286
Original PR description
The `Accounting` dashboard was using very naive formulas to compute deltas between years. Namely, the formulas were based on the assumpution that we'd only compare values year by year but the filters allow to work with quarters or months as well. This revision updates the dashboard file to take the months/quarters into account. task-3957037 Forward-Port-Of: odoo/enterprise#70255 Forward-Port-Of: odoo/enterprise#69286
Remove "Create" and "Create and Edit" of Tax Grids in the list view of Journal Items. task: 4179612 Forward-Port-Of: odoo/enterprise#69864
Original PR description
Remove "Create" and "Create and Edit" of Tax Grids in the list view of Journal Items. task: 4179612 Forward-Port-Of: odoo/enterprise#69864
Problem: The `snailmail_cost` field was not being computed because the compute method was not being called. Steps to reproduce: - Enable "SnailMail" in Settings. - Navigate to Accounting > Follow-up Reports. - Open a report. - Follow up on the report. - Observe that the stamps count is 1, even if the partner has multiple follow-up contacts. opw-4160083 Forward-Port-Of: odoo/enterprise#70236
Original PR description
Problem: The `snailmail_cost` field was not being computed because the compute method was not being called. Steps to reproduce: - Enable "SnailMail" in Settings. - Navigate to Accounting > Follow-up Reports. - Open a report. - Follow up on the report. - Observe that the stamps count is 1, even if the partner has multiple follow-up contacts. opw-4160083 Forward-Port-Of: odoo/enterprise#70236
Reproduce Steps: ---------- 1. Install the Planning module. 2. Navigate to My Planning. 3. Open the Repeat Shift section. 4. Click the Delete button. 5. Click on a radio button label, such as 'This and Following Shifts'. Fixed an issue where clicking the shift option labels did not select the corresponding value. The problem was addressed by setting the `id` attribute on the input element and properly associating it with the label. task-3978567 Forward-Port-Of: odoo/enterprise#
Original PR description
Reproduce Steps: ---------- 1. Install the Planning module. 2. Navigate to My Planning. 3. Open the Repeat Shift section. 4. Click the Delete button. 5. Click on a radio button label, such as 'This and Following Shifts'. Fixed an issue where clicking the shift option labels did not select the corresponding value. The problem was addressed by setting the `id` attribute on the input element and properly associating it with the label. task-3978567 Forward-Port-Of: odoo/enterprise#70143 Forward-Port-Of: odoo/enterprise#68220
### Steps to reproduce issue: 1. Go to _Accounting > Configuration > Account Reports_ 2. Select Balance Sheet and Add a line in it 3. Select the new line and give it ASSETS as parent_id 4. Go to Reporting > Balance Sheet 5. The new line is still at the end of the report ### Explanation: Lines have a `sequence` to sort them in the report. It is not computed to change along with `parent_id`, since the lines are supposed to be arranged through the `AccountReportListRenderer` widget. Be
Original PR description
### Steps to reproduce issue: 1. Go to _Accounting > Configuration > Account Reports_ 2. Select Balance Sheet and Add a line in it 3. Select the new line and give it ASSETS as parent_id 4. Go to Reporting > Balance Sheet 5. The new line is still at the end of the report ### Explanation: Lines have a `sequence` to sort them in the report. It is not computed to change along with `parent_id`, since the lines are supposed to be arranged through the `AccountReportListRenderer` widget. Because of it a line whose `parent_id` changes will not be placed correctly. ### Fix reasoning: The `parent_id` field will be removed from the view, the hierarchy is already shown in the widget. opw-4101282 Forward-Port-Of: odoo/enterprise#69568
This commit's purpose is to force the use of the widget 'taskWithHours' when the timesheet timer is launched. Previously, this was done through the xml by setting the 'type' attribute. This is no longer an option, so instead, we update the arguments given in the getPropertyFieldInfo method on the js side with the type we need. task - 4166816 affected version saas-17.2 - master Forward-Port-Of: odoo/enterprise#69663
Original PR description
This commit's purpose is to force the use of the widget 'taskWithHours' when the timesheet timer is launched. Previously, this was done through the xml by setting the 'type' attribute. This is no longer an option, so instead, we update the arguments given in the getPropertyFieldInfo method on the js side with the type we need. task - 4166816 affected version saas-17.2 - master Forward-Port-Of: odoo/enterprise#69663
- 17.0 ### Steps to reproduce: - Install sale_planning and project_forecast app. - Create a sale order with the planning product (e.g. Developer (Plan services)) and confirm it. - Create planning for that sale order and set resource (e.g. Marc demo) to it. - Click 'Publish & Send' button. - Set 'User: Own Documents Only' rights for the sales and 'User' or 'none' for the project and planning for Marc demo. - Login from that user and open the planning app. - Open assigned planning form v
Original PR description
- 17.0 ### Steps to reproduce: - Install sale_planning and project_forecast app. - Create a sale order with the planning product (e.g. Developer (Plan services)) and confirm it. - Create planning for that sale order and set resource (e.g. Marc demo) to it. - Click 'Publish & Send' button. - Set 'User: Own Documents Only' rights for the sales and 'User' or 'none' for the project and planning for Marc demo. - Login from that user and open the planning app. - Open assigned planning form view. - Print planning. ### Issue: - Traceback occurs of access right. ### Cause: - While downloading the report, it goes to access the "display_name" and "name" field of sale order line and project respectively that is computed in the _compute_display_name, but the user cannot access "sale.order.line" and "project" due to record rule. ### Solution: - Give access to the record by using sudo(). task-3978552 Forward-Port-Of: odoo/enterprise#69533
Currently, an exception is generated when the user tries to upload an image file for creating an invoice. error: `UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte` This is because below code line tries to load image context of uploaded image file. https://github.com/odoo/enterprise/blob/799b80d12680153a5ba42ee97501723ba38052b1/l10n_ke_edi_oscu/models/account_move.py#L567 This commit fixes the above issue by handling `UnicodeDecodeError` in `con
Original PR description
Currently, an exception is generated when the user tries to upload an image file for creating an invoice. error: `UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte` This is because below code line tries to load image context of uploaded image file. https://github.com/odoo/enterprise/blob/799b80d12680153a5ba42ee97501723ba38052b1/l10n_ke_edi_oscu/models/account_move.py#L567 This commit fixes the above issue by handling `UnicodeDecodeError` in `contextlib.suppress.` sentry-5757745777 Forward-Port-Of: odoo/enterprise#69649