Tuesday, August 6, 2024
9 changes · master
Enhancements to existing features
The option to include e-invoices in GSTR1 filings is now tracked when it is changed. This helps businesses keep a clearer audit trail and maintain consistency during GSTR1 submission activities.
Original PR description
before this commit: `gstr1_include_einvoice` field can be enabled/disabled before/after pushing GSTR1 status after this commit: `gstr1_include_einvoice` is now trackable to maintain consistency and maintain logs while pushing GSTR1
Resolved issues and error corrections
The follow-up report address layout has been adjusted so mailed letters meet Pingen's formatting requirements. This helps ensure customer follow-up letters can be processed correctly by the snail mail service.
Original PR description
Moves the address to fit Pingen requirement by applying the class associated styling. Community PR: https://github.com/odoo/odoo/pull/174635 task-4076930
Miscellaneous changes
After making changes in community PR: https://github.com/odoo/odoo/pull/161705 The datetime widget was not being applied when we dragged and dropped a datetime field from the studio. Steps to reproduce: - Open the Sales module and toggle Studio. - Drag and drop a datetime field into the list view. - Try to tick and untick the Show time option. Observed behavior: When ticking and unticking the show time option, the time part is not hiding before resetting the widget. Expected be
Original PR description
After making changes in community PR: https://github.com/odoo/odoo/pull/161705 The datetime widget was not being applied when we dragged and dropped a datetime field from the studio. Steps to reproduce: - Open the Sales module and toggle Studio. - Drag and drop a datetime field into the list view. - Try to tick and untick the Show time option. Observed behavior: When ticking and unticking the show time option, the time part is not hiding before resetting the widget. Expected behavior: The time part should be hidden when we tick and untick the show time option without resetting the widget. After this commit, the datetime widget will be applied when we drag and drop a datetime field from the studio and untick the show time boolean. Task-3698841 Forward-Port-Of: odoo/enterprise#67843 Forward-Port-Of: odoo/enterprise#67258
This fixes a mislabeled placeholder in the payroll salary rule setup so it uses the correct quantity field name. It helps prevent confusion or errors when configuring payroll calculations.
Original PR description
result_quantity is actually called result_qty so the placeholder should reflect that.
Steps ----- [Planning] - Create a shift from 1 July 2024 -> 31 July 2024 and chose the option to repeat it every month. Save it. 1st issue: no shift is created in September. 2nd issue: November shift ends in December and overlaps with December shift. Cause ----- - The 1st issue is caused by the first day of the September shift being on a weekend. In case the first day is not a working day, a shift will only be generated if the first day of the original shift was outside working days.
Original PR description
Steps ----- [Planning] - Create a shift from 1 July 2024 -> 31 July 2024 and chose the option to repeat it every month. Save it. 1st issue: no shift is created in September. 2nd issue: November shift…
Steps ----- [Planning] - Create a shift from 1 July 2024 -> 31 July 2024 and chose the option to repeat it every month. Save it. 1st issue: no shift is created in September. 2nd issue: November shift ends in December and overlaps with December shift. Cause ----- - The 1st issue is caused by the first day of the September shift being on a weekend. In case the first day is not a working day, a shift will only be generated if the first day of the original shift was outside working days. https://github.com/odoo/enterprise/blob/079b0ba241b8b4f7fbd74775e5fc43b27ca3c8fd/planning/models/planning_recurrency.py#L104-L107 - The 2nd issue happens because the length of all the repeated shifts is the same than the original shift. In the case of a longer original month, this will create overlapping generated shifts when we get to shorter months. Introduced by 079b0ba241b8b4f7fbd74775e5fc43b27ca3c8f Fix ----- - Consider a shift with any day (and not just the starting one) outside of working days as being outside working days. - Adapt the length of the generated shifts in case of a monthly recurrence. Take the minimum between the original shift duration in days and the number of days in the month. opw-3996123 Forward-Port-Of: odoo/enterprise#66408
In this commit, we had the partner information to the receipt header of the CL PoS when the order is a factura. This is needed in order to be compliant with the CL law. task-id: 3747828 Forward-Port-Of: odoo/enterprise#67839 Forward-Port-Of: odoo/enterprise#67168
Original PR description
In this commit, we had the partner information to the receipt header of the CL PoS when the order is a factura. This is needed in order to be compliant with the CL law. task-id: 3747828 Forward-Port-Of: odoo/enterprise#67839 Forward-Port-Of: odoo/enterprise#67168
Fix singleton error Steps: - Go to follow-up report - Select 2 partners in the list view - Select "Print Customer Statements" in the action menu -> Singleton error opw-4075655 Forward-Port-Of: odoo/enterprise#67610
Original PR description
Fix singleton error Steps: - Go to follow-up report - Select 2 partners in the list view - Select "Print Customer Statements" in the action menu -> Singleton error opw-4075655 Forward-Port-Of: odoo/enterprise#67610
Currently, log level error message occur when no company is found during scheduled actions run at line [1]. This commit changes 'logger.error' to 'logger.warning' to log a message instead of an error since this is not an actual error in the code base. [1]-https://github.com/odoo/enterprise/blob/ddc81ed35a6738739647db868c13236673695cff/l10n_ke_edi_oscu/models/res_company.py#L437-L438 sentry-5608113473 Forward-Port-Of: odoo/enterprise#66799
Original PR description
Currently, log level error message occur when no company is found during scheduled actions run at line [1]. This commit changes 'logger.error' to 'logger.warning' to log a message instead of an error since this is not an actual error in the code base. [1]-https://github.com/odoo/enterprise/blob/ddc81ed35a6738739647db868c13236673695cff/l10n_ke_edi_oscu/models/res_company.py#L437-L438 sentry-5608113473 Forward-Port-Of: odoo/enterprise#66799
The cancel_shipment method name is incorrect, due to the leading _ which causes it to not be picked up when cancelling a picking. This means that starshipit packages do not get archived automatically when cancelling then in Odoo, as you would expect them to be. Task id # 4074169 Forward-Port-Of: odoo/enterprise#67927
Original PR description
The cancel_shipment method name is incorrect, due to the leading _ which causes it to not be picked up when cancelling a picking. This means that starshipit packages do not get archived automatically when cancelling then in Odoo, as you would expect them to be. Task id # 4074169 Forward-Port-Of: odoo/enterprise#67927