Friday, November 10, 2023
14 changes · master
Miscellaneous changes
Steps: - Install project, timesheet & website - Open project module - Select any task - Set Allocated Hours - Go to the task corresponding project & disable the timesheet - Then error is appear in portal form view Issue: - In portal form view of project's task the 'allocated time' and the 'progress' fields shouldn't be visible if the 'timesheets' feature is disabled on the project. Cause: - There is no any condition for allocated time and progress field. Fix: - Added t-if="tim
Original PR description
Steps: - Install project, timesheet & website - Open project module - Select any task - Set Allocated Hours - Go to the task corresponding project & disable the timesheet - Then error is appear in portal form view Issue: - In portal form view of project's task the 'allocated time' and the 'progress' fields shouldn't be visible if the 'timesheets' feature is disabled on the project. Cause: - There is no any condition for allocated time and progress field. Fix: - Added t-if="timesheets and allow_timesheets" condition for both field in hr_timesheet & project respectively. Task-3495253 Forward-Port-Of: odoo/odoo#141357 Forward-Port-Of: odoo/odoo#133437
Task 3300854 would remove the "add a to-do" action in the systray, but by doing so, it removed the action in the command palette as well. This PR will re-add the action in the command palette. The ActivityMenu component is patched to call "useCommand" and add the command to the command palette each time it is loaded. task-3580533 Forward-Port-Of: odoo/odoo#141168
Original PR description
Task 3300854 would remove the "add a to-do" action in the systray, but by doing so, it removed the action in the command palette as well. This PR will re-add the action in the command palette. The ActivityMenu component is patched to call "useCommand" and add the command to the command palette each time it is loaded. task-3580533 Forward-Port-Of: odoo/odoo#141168
Before this commit, in the settings page on mobile mode, when swiping between the different apps, on the app selector the current app stay selected on the right corner. The selected app will stay on top of the other apps, and the app selector itself didn't move. Now, when swiping between the different apps, the app selector moves to force the current app to be in the center of the selector. task-id: 3489756 Forward-Port-Of: odoo/odoo#141524 Forward-Port-Of: odoo/odoo#141140
Original PR description
Before this commit, in the settings page on mobile mode, when swiping between the different apps, on the app selector the current app stay selected on the right corner. The selected app will stay on top of the other apps, and the app selector itself didn't move. Now, when swiping between the different apps, the app selector moves to force the current app to be in the center of the selector. task-id: 3489756 Forward-Port-Of: odoo/odoo#141524 Forward-Port-Of: odoo/odoo#141140
pricelist item variant group by filter to actually group by variant the variant field is `product_id`. Current behavior before PR:  Desired behavior after PR is merged:  @ForgeFlow --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: od
Original PR description
pricelist item variant group by filter to actually group by variant the variant field is `product_id`. Current behavior before PR:  Desired behavior after PR is merged:  @ForgeFlow --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139747
Steps to reproduce: ------------------- - add lunchtime in an employee's calendar; - in Attendance app, add attendance for this employee for last month; (The hours calculated in the attendances take into account the lunchtime.) - go to the form view of this employee; Issue: ------ The statistics button, which displays the hours worked last month, does not take into account lunchtimes. Cause: ------ To find the hours worked, we calculate the difference between the `check_in` and th
Original PR description
Steps to reproduce: ------------------- - add lunchtime in an employee's calendar; - in Attendance app, add attendance for this employee for last month; (The hours calculated in the attendances take into account the lunchtime.) - go to the form view of this employee; Issue: ------ The statistics button, which displays the hours worked last month, does not take into account lunchtimes. Cause: ------ To find the hours worked, we calculate the difference between the `check_in` and the `check_out`. Solution: --------- Use the `worked_hours` field of attendance, which takes into account the employee's calendar and therefore lunchtimes. opw-3547521 Forward-Port-Of: odoo/odoo#141282 Forward-Port-Of: odoo/odoo#140629
When submitting invoices with a foreign partneer using the fiscal device, the device will throw an error when the VAT number is not formatted as per the Kenyan VAT number. In this case, we should only send the vat number when it matches the format of a Kenyan VAT number. opw-3557736 Forward-Port-Of: odoo/odoo#140381
Original PR description
When submitting invoices with a foreign partneer using the fiscal device, the device will throw an error when the VAT number is not formatted as per the Kenyan VAT number. In this case, we should only send the vat number when it matches the format of a Kenyan VAT number. opw-3557736 Forward-Port-Of: odoo/odoo#140381
Before this commit, a component couldn't be mounted on a public widget that wasn't yet attached in the dom. Forward-Port-Of: odoo/odoo#141665
Original PR description
Before this commit, a component couldn't be mounted on a public widget that wasn't yet attached in the dom. Forward-Port-Of: odoo/odoo#141665
Setting a default value for an integer that is greater than that allowed by a 32-bit integer raises an error when we save a new record so it isn't clear that the issue comes from the default value Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts and open any contact 3. Toggle Studio and add an integer field in the view 4. In the Studio sidebar, set the default value to 3 000 000 000 5. Save and close Studio 6. Create a new contact, give it a name and try to save the
Original PR description
Setting a default value for an integer that is greater than that allowed by a 32-bit integer raises an error when we save a new record so it isn't clear that the issue comes from the default value Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts and open any contact 3. Toggle Studio and add an integer field in the view 4. In the Studio sidebar, set the default value to 3 000 000 000 5. Save and close Studio 6. Create a new contact, give it a name and try to save the record 7. An error is thrown Solution: Raise an error if we set an integer field's default value out of the bounds of a 32-bit integer opw-3360160 Forward-Port-Of: odoo/odoo#141339 Forward-Port-Of: odoo/odoo#139189
Description of the issue/feature this PR addresses: * Sum rank fields if the partner is merged It will help to increase the rank of both records and have a better ranking Current behavior before PR: When partners are merged, the records of sales and invoices are merged also, but the rank fields are not updated, so it has incongruent information. Desired behavior after PR is merged: When partners are merged, the records of sales and invoices are merged, ranks fields are updated
Original PR description
Description of the issue/feature this PR addresses: * Sum rank fields if the partner is merged It will help to increase the rank of both records and have a better ranking Current behavior before PR: When partners are merged, the records of sales and invoices are merged also, but the rank fields are not updated, so it has incongruent information. Desired behavior after PR is merged: When partners are merged, the records of sales and invoices are merged, ranks fields are updated correctly. ----- Update branch of this https://github.com/odoo/odoo/pull/85562 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#141366
If a .map is missing (outdated) the error message will report 'min' expected in extension in non debug mode when the problem is actually that map are not generate through this route. If the attachment corresponding to a .map is not found, it was most likely garbage collected. Change the message to: .map should have been generated through debug assets, (version 5eff983 most likely outdated) Forward-Port-Of: odoo/odoo#141469
Original PR description
If a .map is missing (outdated) the error message will report
'min' expected in extension in non debug mode
when the problem is actually that map are not generate through this route.
If the attachment corresponding to a .map is not found, it was most likely garbage collected.
Change the message to:
.map should have been generated through debug assets, (version 5eff983 most likely outdated)
Forward-Port-Of: odoo/odoo#141469Since [1], when an error exists in an asset, the assets raise a not found exception. The issue, is that, there is no feedback for the developer to find the error. Now, a new console log with the error details is shown. [1] : bf3b6b0b8b2277757b242b28c65c05433632f467 Forward-Port-Of: odoo/odoo#141705
Original PR description
Since [1], when an error exists in an asset, the assets raise a not found exception. The issue, is that, there is no feedback for the developer to find the error. Now, a new console log with the error details is shown. [1] : bf3b6b0b8b2277757b242b28c65c05433632f467 Forward-Port-Of: odoo/odoo#141705
With the last changes on the TIM_2 the base for the RteIVA (Code '05') Tax is being computed with Invoice base_mount, but for the case of this particular Tax, the base needs to be comouted using the Tax amout it self. Here is an example of the output as it should be: https://drive.google.com/file/d/153lbY51GyrTJaSDfea2OQVD4aE3Tx1ya/view?usp=sharing Forward-Port-Of: odoo/enterprise#50488 Forward-Port-Of: odoo/enterprise#50339
Original PR description
With the last changes on the TIM_2 the base for the RteIVA (Code '05') Tax is being computed with Invoice base_mount, but for the case of this particular Tax, the base needs to be comouted using the Tax amout it self. Here is an example of the output as it should be: https://drive.google.com/file/d/153lbY51GyrTJaSDfea2OQVD4aE3Tx1ya/view?usp=sharing Forward-Port-Of: odoo/enterprise#50488 Forward-Port-Of: odoo/enterprise#50339
Before this commit, the default planned dates were not set when creating a task from the gantt view in field service. As the default planned dates when creating a task from fsm should not be different than from project, we delete the default_get code concerning the planned dates in FSM and we apply the same default as for normal tasks. task-3576701 task-3586078 Forward-Port-Of: odoo/enterprise#50284
Original PR description
Before this commit, the default planned dates were not set when creating a task from the gantt view in field service. As the default planned dates when creating a task from fsm should not be different than from project, we delete the default_get code concerning the planned dates in FSM and we apply the same default as for normal tasks. task-3576701 task-3586078 Forward-Port-Of: odoo/enterprise#50284
Add the missing neutralisation script for the module l10n_be_codabox introduced in v17 with https://github.com/odoo/enterprise/pull/47607 Forward-Port-Of: odoo/enterprise#49738
Original PR description
Add the missing neutralisation script for the module l10n_be_codabox introduced in v17 with https://github.com/odoo/enterprise/pull/47607 Forward-Port-Of: odoo/enterprise#49738