Friday, November 26, 2021
41 changes · master
Enhancements to existing features
Survey authors can now add placeholder guidance for questions that require typed input. This helps participants understand what kind of answer is expected, improving clarity and response quality.
Original PR description
Purpose ======= As an Interviewer, I want my questions to be as clear as possible. To this end, I would like to be able to detail a bit which kind of answers I expect. Specifications ============ For all the question types that require an input, display a char field "Placeholder" in the Answers tab with a field helper that says: "When set, this text will appear in the field to help participants answer." Then on the survey, display the placeholder in the question input zone. Task-2671388
The Survey app now offers ready-made sample surveys for feedback forms, live presentations, and certifications when users first get started. This helps business users create useful surveys faster by starting from a pre-configured template they can adapt to their needs.
Original PR description
When the user opens the survey module for the first time, the user may find it difficult to create and configure a new survey as there are many options available. To improve the onboarding experience of the user, we will provide a new link on the action helper of the survey module (for the kanban and the list view of the surveys). When the user clicks on that link, the system will open a new modal. The user will then be able to choose a sample to load. Each sample will be pre-configured for specific purposes. We will have: - A sample for the feedback forms - A sample for the live presentations - A sample for the certifications After loading a sample, the user will be able to adapt it to fit their needs. Thanks to the samples, the user can create a survey more easily and more quickly. task-2670605 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The settings screen now avoids unnecessary background work when opening or saving configuration changes. This makes common settings actions noticeably faster and reduces database load, especially in larger Odoo installations with many modules enabled.
Original PR description
Improve the res.config.settings wizard performance, on the python side (focus on `onchange`, `create` and `execute` rpcs). * Avoid modification of non modified settings * Do not fetch unnecessary data: * Use cached methods to avoid verifying n times the existence of a given record * Do not compute requested defaults if not asked by the ORM. Before this PR: on runbot with "all" modules: onchange: 0.6 sec create: 0.53 s execute (call_button): 0.59 s After: onchange: 0.27 sec create: 0.31 sec execute: 0.28 sec and up to 3* less queries -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project duplication now carries over milestones while resetting completion and deadline details, making copied projects easier to reuse accurately. Sales order screens were also adjusted to present status actions in a clearer order, improving day-to-day navigation for users.
Original PR description
The purpose of the commit is to do the generic improvement for the project: So in this commit, do the following changes: - duplicating a project, copy all milestones of the project, and set is_reached and deadline field as 'False'. - change the order of the state button in the sale order form view task-2652943
The employee timesheet cost field label has been shortened from “Timesheet Cost” to “Cost.” This makes the employee form wording cleaner and easier to read without changing any underlying functionality.
Original PR description
hr_timesheet: rename the string of timesheet_cost field in employee - The string of timesheet_cost field is cost instead of Timesheet Cost. task-2531442 closes odoo/odoo#79016
Changing a customer's price list now shows a warning if that customer has open shopping carts that will not be updated automatically. This helps staff avoid pricing confusion by making it clear when open carts need to be adjusted manually.
Original PR description
It is not always immediately clear to the end user that changing the pricelist on a partner will not change the pricelist for any open carts related to this partner. To clarify, this commit introduces a warning message, indicating that the end user should change the pricelists of these open carts manually if this is the desired effect.
Any open carts that already have the same pricelist as the new partner pricelist are excluded from the search and will not trigger the warning message.
task-2635067This update improves several inventory, delivery, sales, purchase, and product workflows by making fields clearer, filters easier to use, and replenishment actions more reliable. It also fixes confusing links and labels in stock reports and helps prevent setup mistakes such as unit categories without a reference unit.
Original PR description
In this commit: ================================== 1. Added domain to display only product related variants in the product view 2. Added a Trigger Manual filter in the existing filter list of…
In this commit:
==================================
1. Added domain to display only product related variants in the product view
2. Added a Trigger Manual filter in the existing filter list of Replenishment view
3. Added a logic to set deadline date of DO based on the SO deadline date in sale
4. Changed the error message string if the same product record already exists in the replenishment
5. Changed the string of lot_name field in the stock move
6. Fixed Forecast Report breadcrumbs issue
7. Fixed Lost label of product on replenishment report while reserve/unreserve the quantity of product
8. Added logic to force user to set at least one unit as a Reference Unit in UoM category units
9. Changed the string of dhl delivery module from DHL USA to DHL Express
10. Added logic to set default product quantity value in product replenishment wizard
11. Fixed the issue of Manufacturing Order link showing html tag instead of link in replenishment view
12. Added a two view files to delivery module
1. stock_rule_view: to display the propagate_carrier field
2. stock_picking_type_view: to display the print_label field
13. Fixed the issue of Purchase Order link showing html tag instead of link in replenishment view
14. Fixed the issue of showing html tag in line
15. Moved propagate_carrier field to delivery module.
TaskID - 2581265
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCRM reporting now shows all leads and opportunities, even when the separate Leads feature is not enabled. This gives managers a broader view of CRM activity, with clearer default grouping and report columns to understand lead type, stage, and performance.
Original PR description
Purpose
=======
As a Lead Manager, I do not really care about what's in the "Lead Pipeline"
since this does not exist. Instead, I want to keep an eye on all the leads that
entered the CRM to see how well they are doing and how they are spread.
Specifications
==============
- Remove the group on the Reporting
> Leads menu item, this menu can be used with Opportunities only
- Move it below the Pipeline report
- By default, this menu shows all crm.lead :
- no matter the type (lead/opp) but with the filters in the search view
if needed
- no matter if won/active/lost (but again, filters allow me to change that
if needed)
- Default grouped by month creation date
- Filtered on records created this year to avoid displaying 10 years of CRM
usage - already done
=> The difference if I activate leads is that then I have the extra filters, ...
but this is already valid if I'm only working with opportunities
Task-2671372The Planning Analysis report now includes cost measures for allocated and effective hours, making it easier to compare planned work with actual effort. The report layout and graph ordering were adjusted for clearer analysis, and wording around working days was simplified.
Original PR description
Planning Analysis Report - Added 'Allocated Hours Cost' and 'Effective Hours Cost' measures - in the Planning Analysis report. - Removed 'hours per employee' filter and default group by the employee. - Set descending order in graph of planning analysis. - The string of the timesheet_cost field has been changed to 'Working Days' - instead of 'Number of Working Days'. closes odoo#21900 task-2531442
Warehouse users can now add the quantity for a product package directly from a barcode operation line. This reduces extra steps by avoiding the need to open the detailed edit view for each stock move line.
Original PR description
Add a new button for operations in the Barcode app. It allows to add the quantity corresponding to the Product Packaging of the Stock Move Line directly instead of going in the 'edit' view of the Stock Move Line. Task-ID: 2659768
Planning and service workflows were refined to make schedules, task details, and related sales or ticket information clearer for users. The update improves calendar visibility, button placement, staff avatars, and demo planning data so teams can navigate service operations more easily.
Original PR description
planning,industry_fsm,sale_planning,project_forecast,helpdesk_sale_timesheet Purpose of this commit to improve generic UX for service apps. So, In this commit done following changes: - replace 'after' with 'before' in xpath where data_start field added in kanban view of project task in field service app. - assign shifts to different project and SOLS in 'project_forcest' and 'sale_planning' respectively. Add more SOLS to plan for different roles in 'sale_palnning'. - add many2one_avatar widget for resource_id field in form view and calendar view popover of planning.slot model - invisible the state field in calendar view of 'Schedule' and 'My Planning' menu. - move 'I TAKE IT' button to right of the 'PUBLISH' button. - added 'Plain' and 'Draft' legend in calendar view. - move Tickets state button after Tasks state button. task-2652943
The Documents app test coverage was adjusted so access rights are checked before confirming follower display behavior. This helps ensure follower information is shown correctly and consistently for users with the right permissions.
Original PR description
Checking access rights and returning true in testcase to display followers correctly.
Users can now control the order of lines in a subscription. This makes subscription details easier to organize and present in the preferred sequence.
Original PR description
Before this commit you cannot order line in subscription. @tde-banana-odoo
Resolved issues and error corrections
The French localization setup removes obsolete negative tax groups that should not be used. This restores a prior cleanup so taxes remain assigned to the correct standard tax groups, reducing confusion in accounting configuration.
Original PR description
These negative tax groups were removed in a previous commit: 1687248 The message of the previous commit was: Remove the negative tax groups from account_data. The negative tax groups have no application. The taxes that were in the negative tax groups are reassigned to their positive counterparts. The previous commit was accidentally overwritten in a forward-port: odoo#77295 closes odoo#76586
Code cleanup and technical improvements
Odoo now calculates certain stored fields before a record is first saved, making it possible to require those values and enforce database rules on them. This improves data reliability across core models while keeping exceptions for fields that still need to be calculated after creation.
Documentation and clarification updates
This update records the corporate contributor agreement signature for Strong Blue Conseil & Telecom. It supports Odoo's legal compliance process by documenting the company's authorization to contribute to the project.
Original PR description
CLA signature for Strong Blue Conseil & Telecom
Miscellaneous changes
When editing the billing address of an existing portal partner P, the salesperson of P was changed by the default website salesperson opw:2649732 Forward-Port-Of: odoo/odoo#80349
Original PR description
When editing the billing address of an existing portal partner P, the salesperson of P was changed by the default website salesperson opw:2649732 Forward-Port-Of: odoo/odoo#80349
Blog post cover titles now use the main page heading format, helping search engines better identify the post title. This small change improves SEO clarity while keeping the visual style consistent for related blog covers.
Original PR description
SEO issue: blog post doesn't have `<h1>` for post title. The goal of this PR is to change "first cover" title to `<h1>`. "Next blog" cover title will have a h1 style too. task-2454130
When SEPA batch booking is enabled, payment batches now use the batch date instead of each individual payment date. This helps banks process the batch as a single transaction, reducing duplicate statement lines and making reconciliation easier for accounting teams.
Original PR description
Before this commit if payments in batch have not the same date, the bank doesn't apply the batch in one time (even if sct_batch_booking is True). It is an issue because, one batch generate multi statement line (one per payment date), and it is not possible to reconcile. - Go to runbot: - Create a batch payment with 100 payments dated of 12/05 and 150 payments dated of 21/05, with sct_batch_booking = True - Validate the batch - Import XML in bank system - After a few day you import two bank statement line (one date of 12/05 and an other 21/05) - Open the reconciliation widget, select first line (dated of 12/05) select the batch - --> Issue you should un-select all payments dated of 21/05 With huge volume of payment, it is not usefull. This PR force the date of payment. @oco-odoo Note : can be merge in master if needed
Original PR description
Currently, the computed fields are computed after record creation in DB. This means that computed fields cannot be required and that no SQL constraints can be based on those fields. To support…
Currently, the computed fields are computed after record creation in DB. This means that computed fields cannot be required and that no SQL constraints can be based on those fields. To support required and sql constraints on computed (and stored) fields, we need to compute the fields before record creation ... ### Side features/changes ##### `_pre_compute` model attribute Specify a model as `_pre_compute=True` to enable computed fields computation before record creation. Added to make the feature OPT-IN, allowing us to convert models one by one when there is a gain to pre_compute their computed fields. ##### `pre_compute` field attribute Specify fields as `pre_compute=False` to ensure they are computed after record creation * Done by default if any compute dependency is `pre_compute=False` * Done by default if field depends on `create_date/write_date/create_uid/write_uid` * Done manually for part of existing fields (mainly statistics fields) ##### Postpone NOT NULL AND SQL constraints after fields/models computation/setup Column are set to NOT NULL after fields computation in DB to ensure model extension with required computed fields works fine. ##### New Record cannot impact real records And inversely To pre-compute computed stored fields, we instantiate a new record with the values given to the create call. This meant that two records were put in cache for one creation (one real and one new). When a record is created linking to real records in o2m or m2m fields, the inverse was triggered and you could have new records in the relational fields of real records. Example: Create an `account.move.line`, linking to real `account.move` 1, if you accessed the lines from the `account.move`, you would receive 2 records (one new and one real). To ensure the new `new()` call in the `create()` method doesn't impact real records, the inverse of new (resp. real) records changes is not applied on real (resp. new) records anymore. It was already the strategy of the orm, but is more strictly applied from now on. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The currency.compute method is deprecated. We use _convert 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 Forward-Port-Of: odoo/odoo#80336
Original PR description
The currency.compute method is deprecated. We use _convert 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 Forward-Port-Of: odoo/odoo#80336
Before this fix, all moves of type “entry“ were considered as misc operations in regard to repartition tags and the tax report. And only moves of type “out_refund” and “in_refund” were considered refunds. Now reverse entries with sale/purchase taxes get their tags set accordingly to repartition lines. ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 0 1000 21% -03 451000 T.V.A. à payer
Original PR description
Before this fix, all moves of type “entry“ were considered as misc operations in regard to repartition tags and the tax report. And only moves of type “out_refund” and “in_refund” were considered…
Before this fix, all moves of type “entry“ were considered as misc operations in regard to repartition tags and the tax report. And only moves of type “out_refund” and “in_refund” were considered refunds. Now reverse entries with sale/purchase taxes get their tags set accordingly to repartition lines. ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 0 1000 21% -03 451000 T.V.A. à payer 0 210 -54 400000 Clients 1210 0 ``` Was reversed to: ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 1000 0 21% -03 451000 T.V.A. à payer 210 0 -54 400000 Clients 0 1210 ``` Is now reversed to: ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 1000 0 21% +49 451000 T.V.A. à payer 210 0 +64 400000 Clients 0 1210 ``` Task: 2687215 Forward-Port-Of: odoo/odoo#80058 Forward-Port-Of: odoo/odoo#79556
Instead of "saving" the state into the DOM (which is lost at next render) save the state of each button in JS. task-2308951 Forward-Port-Of: odoo/odoo#80334
Original PR description
Instead of "saving" the state into the DOM (which is lost at next render) save the state of each button in JS. task-2308951 Forward-Port-Of: odoo/odoo#80334
remove useless console.log -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#80414
Original PR description
remove useless console.log -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#80414
Previously, when underconsumption occured, we split the move (in post_inventory). And if backorder, the moves not done would be linked to the new backorder MO (when backorder MO is created). After 8883c06ada8a7c1debabce39e8f7fea321c70b23, we create backorder MOs before _post_inventory, making it so the moves not done will not be linked to the backorder MOs and reserved qtys are not released. To fix, we set cancel_backorder to be true to cancel all the leftover moves and release the reserv
Original PR description
Previously, when underconsumption occured, we split the move (in post_inventory). And if backorder, the moves not done would be linked to the new backorder MO (when backorder MO is created). After 8883c06ada8a7c1debabce39e8f7fea321c70b23, we create backorder MOs before _post_inventory, making it so the moves not done will not be linked to the backorder MOs and reserved qtys are not released. To fix, we set cancel_backorder to be true to cancel all the leftover moves and release the reserved qty. Task-2697611 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 Forward-Port-Of: odoo/odoo#80271
Before this commit the trigram search would fail if it encounters a (SQL) NULL text from the database. This is because when word_similarity() receives NULL as a parameter it returns NULL, and NULL not being a number cannot be compared with the similarity threshold. After this commit the trigram search will exclude matches returning a NULL similarity. opw-2680659 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged:
Original PR description
Before this commit the trigram search would fail if it encounters a (SQL) NULL text from the database. This is because when word_similarity() receives NULL as a parameter it returns NULL, and NULL not being a number cannot be compared with the similarity threshold. After this commit the trigram search will exclude matches returning a NULL similarity. opw-2680659 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 Forward-Port-Of: odoo/odoo#80050
Issue: The way we generate the dayNamesMin is not compatible with the chineese translation provided by "moment.js". This is because the dayNamesShort contains an extra character in front 週 (week). Because of that the names of the days on the small calendar are all the character 週 (week). Solution: There is a variable (weekdaysMin) which is unused and contain a shorter version of the days this variable is consitent in the other languages so it should have no side effect and will fix th
Original PR description
Issue: The way we generate the dayNamesMin is not compatible with the chineese translation provided by "moment.js". This is because the dayNamesShort contains an extra character in front 週 (week). Because of that the names of the days on the small calendar are all the character 週 (week). Solution: There is a variable (weekdaysMin) which is unused and contain a shorter version of the days this variable is consitent in the other languages so it should have no side effect and will fix the chinese translation as it only contains one character. Introduced by: 1fc33a63beb20d134081c93852e62f5fe0ff67d4 task-2692910 **  ** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#80363
Issue: 1- Website editor > Set shape on image 2- Crop > shape is reapplied on the croped image 3- Change another option (e.g. image width) 4- Undo > image will be shown cropped but without any shape applied on it. In the current code we apply shapes on cropped images using the event listener 'ImageOptimize > _onImageCropped', so in 'ImageTools', the 'crop()' option method will record the "crop" action but the step where the shape is added is lost. (see `SnippetOptionWidget` > `_onU
Original PR description
Issue: 1- Website editor > Set shape on image 2- Crop > shape is reapplied on the croped image 3- Change another option (e.g. image width) 4- Undo > image will be shown cropped but without any shape applied on it. In the current code we apply shapes on cropped images using the event listener 'ImageOptimize > _onImageCropped', so in 'ImageTools', the 'crop()' option method will record the "crop" action but the step where the shape is added is lost. (see `SnippetOptionWidget` > `_onUserValueUpdate`). The goal of this PR is to move the shapes related logic to a "mixin" (for all widgets handeling image shapes), so we can simply use its methods to apply shapes when the 'crop()' method is called. This way, the step to record will be a "cropped image with a shape on it" instead of just a "cropped image". task-2628964 Forward-Port-Of: odoo/odoo#76100
Current behavior before PR: When trying to select emoji on log note before record creation, it shows traceback. Desired behavior after PR is merged: Hiding the emoji button when the record is under creation. Task-2664700 Forward-Port-Of: odoo/odoo#79554
Original PR description
Current behavior before PR: When trying to select emoji on log note before record creation, it shows traceback. Desired behavior after PR is merged: Hiding the emoji button when the record is under creation. Task-2664700 Forward-Port-Of: odoo/odoo#79554
**Current behavior before PR:** Currently, in Discuss, the chat activates the drop zone when try to drag and drop any user's avatar (or any text). The same thing happens if we do it in the chat window or chatter. **Desired behavior after PR is merged:** The chat will not be activated drop zone if the drag is not actually a file/a document. Task-2590510 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#7346
Original PR description
**Current behavior before PR:** Currently, in Discuss, the chat activates the drop zone when try to drag and drop any user's avatar (or any text). The same thing happens if we do it in the chat window or chatter. **Desired behavior after PR is merged:** The chat will not be activated drop zone if the drag is not actually a file/a document. Task-2590510 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73466
This pull request contains 3 commits that fix some behaviours that appeared in 15.0: ### Commit 1 : [FIX] website: restore scrollbar for some menus After [1], the dropdown menu of the main navbar for certains menus (e.g customize on /shop) didn't have scrollbars anymore, making it hard to navigate on smaller resolution devices. This commit restores that. [1] : 1971bf39810468b2b67e2ecd3c86c663d5cffcfd --- ### Commit 2 : [FIX] website: always display build my website button Thi
Original PR description
This pull request contains 3 commits that fix some behaviours that appeared in 15.0: ### Commit 1 : [FIX] website: restore scrollbar for some menus After [1], the dropdown menu of the main navbar for…
This pull request contains 3 commits that fix some behaviours that appeared in 15.0: ### Commit 1 : [FIX] website: restore scrollbar for some menus After [1], the dropdown menu of the main navbar for certains menus (e.g customize on /shop) didn't have scrollbars anymore, making it hard to navigate on smaller resolution devices. This commit restores that. [1] : 1971bf39810468b2b67e2ecd3c86c663d5cffcfd --- ### Commit 2 : [FIX] website: always display build my website button This commit moves the position of the build my website button in the configurator so that it's always visible, even with low resolution displays and mobile phones --- ### Commit 3 : [FIX] web_editor: fix gradient slider infinite resize and safari support Prior to this commit, if three colors were selected for a gradient and the user would click on the third color, if that color had a value of 100%, in certain condition the picker would resize infinitely. Also prior to this commit, the color picker slider was not supported well under safari This commit fixes the SCSS rules in order to fix those behaviours. task-2670809 Forward-Port-Of: odoo/odoo#78694
Prevent calling _get_sequence_format_param() with None as parameter in _is_end_of_seq_chain() when sequence is empty. Would cause an error when deleting an invoice with an empty sequence. Task: 2697771 Forward-Port-Of: odoo/odoo#80235
Original PR description
Prevent calling _get_sequence_format_param() with None as parameter in _is_end_of_seq_chain() when sequence is empty. Would cause an error when deleting an invoice with an empty sequence. Task: 2697771 Forward-Port-Of: odoo/odoo#80235
**Steps to follow** - Share a project task -> The invitation message is duplicated **Cause of the issue** `partners` can be empty -> `not partners` is then falsy **Solution** Check the default parameter with `is None` opw-2698724 Forward-Port-Of: odoo/odoo#80422
Original PR description
**Steps to follow** - Share a project task -> The invitation message is duplicated **Cause of the issue** `partners` can be empty -> `not partners` is then falsy **Solution** Check the default parameter with `is None` opw-2698724 Forward-Port-Of: odoo/odoo#80422
Same as 5dde19c92ecee, sudo is not enough but the report needs to rendered with the user 1. The access token proves the user has the access, the fact that he is a portal, employee or public should not change the result Forward-Port-Of: odoo/odoo#80485 Forward-Port-Of: odoo/odoo#80465
Original PR description
Same as 5dde19c92ecee, sudo is not enough but the report needs to rendered with the user 1. The access token proves the user has the access, the fact that he is a portal, employee or public should not change the result Forward-Port-Of: odoo/odoo#80485 Forward-Port-Of: odoo/odoo#80465
Some bank create ofx file with a the sort account number (not the full IBAN). The import wizard doesn't find the journal. - create a journal with IBAN bank account (like FR76XXXX68655578980XXX) - Try to import an ofx file formated like that: ``` <OFX> <BANKMSGSRSV1> <STMTTRNRS> <TRNUID> 66046425880 <STATUS> <CODE> 0 <SEVERITY>INFO </STATUS>
Original PR description
Some bank create ofx file with a the sort account number (not the full IBAN). The import wizard doesn't find the journal. - create a journal with IBAN bank account (like FR76XXXX68655578980XXX) - Try…
Some bank create ofx file with a the sort account number (not the full IBAN). The import wizard doesn't find the journal.
- create a journal with IBAN bank account (like FR76XXXX68655578980XXX)
- Try to import an ofx file formated like that:
```
<OFX>
<BANKMSGSRSV1>
<STMTTRNRS>
<TRNUID>
66046425880
<STATUS>
<CODE>
0
<SEVERITY>INFO
</STATUS>
<STMTRS>
<CURDEF>
EUR
<BANKACCTFROM>
<BANKID>
16336
<BRANCHID>
09811
<ACCTID>
68655578980
<ACCTTYPE>CHECKING
</BANKACCTFROM>
<BANKTRANLIST>
<DTSTART>
20210416000000
<DTEND>
```
Odoo use ACCTID to get the account number. But ACCTID != IBAN
- the journal is not found
@oco-odoo
Co-Authored-By: oco-odoo <oco@odoo.com>
Forward-Port-Of: odoo/enterprise#22539What are the steps to reproduce this behavior? - Create a shift >> Enable the shift to be recurring and Until >> Set End Date to any date >> Publish Then click on the shift >> Change the end date to either before or after What is the behavior that is occurring? - You're provided with a traceback and the shift end date is not changed. What is the expected behavior for this flow? - There shouldn't be a traceback and the shift end date to be adjusted. opw-2692187 Forward-Port-Of: od
Original PR description
What are the steps to reproduce this behavior? - Create a shift >> Enable the shift to be recurring and Until >> Set End Date to any date >> Publish Then click on the shift >> Change the end date to either before or after What is the behavior that is occurring? - You're provided with a traceback and the shift end date is not changed. What is the expected behavior for this flow? - There shouldn't be a traceback and the shift end date to be adjusted. opw-2692187 Forward-Port-Of: odoo/enterprise#22461
1. Enter a bank statement line and reconcile the line using “Manual Operations” with a sales tax (included) component. 2. Run the Tax Report and the tax value is correct under the tax code specified. 3. Open the audit report. The base amount is zero for this transaction. This occur because the value of the base amount is not sent with other line values to the backend opw-2638224 Forward-Port-Of: odoo/enterprise#22331
Original PR description
1. Enter a bank statement line and reconcile the line using “Manual Operations” with a sales tax (included) component. 2. Run the Tax Report and the tax value is correct under the tax code specified. 3. Open the audit report. The base amount is zero for this transaction. This occur because the value of the base amount is not sent with other line values to the backend opw-2638224 Forward-Port-Of: odoo/enterprise#22331
Prevent pypdf2 from crashing when merging some pdf pages with sign pages as some PDF generators are building PDF streams with invalid numbers Here are some tickets related to that problem : -->[2680714](https://www.odoo.com/web#id=2680714&action=3530&model=project.task&view_type=form&cids=1&menu_id=4720) -->[2568744](https://www.odoo.com/web#id=2568744&model=project.task&view_type=form&cids=1&menu_id=5195) -->[2673998](https://www.odoo.com/web#id=2673998&cids=1&model=project.task&view_ty
Original PR description
Prevent pypdf2 from crashing when merging some pdf pages with sign pages as some PDF generators are building PDF streams with invalid numbers Here are some tickets related to that problem : -->[2680714](https://www.odoo.com/web#id=2680714&action=3530&model=project.task&view_type=form&cids=1&menu_id=4720) -->[2568744](https://www.odoo.com/web#id=2568744&model=project.task&view_type=form&cids=1&menu_id=5195) -->[2673998](https://www.odoo.com/web#id=2673998&cids=1&model=project.task&view_type=form) The problem still exists in 15.0 so this PR should be forwardported. Forward-Port-Of: odoo/enterprise#22314
Before this entries (move of type 'entry') on sale journal would have their amount inversed incorectly. An entry on a sale journal : ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 0 1000 21% -03 451000 T.V.A. à payer 0 210 -54 400000 Clients 1210 0 ``` Would have had negative amounts on lines 03 and 53 before this fix. Task: 2687215 Fo
Original PR description
Before this entries (move of type 'entry') on sale journal would have their amount inversed incorectly. An entry on a sale journal : ``` Account D C Tax Tax Grids 700000 Ventes en Belgique (marchandises) 0 1000 21% -03 451000 T.V.A. à payer 0 210 -54 400000 Clients 1210 0 ``` Would have had negative amounts on lines 03 and 53 before this fix. Task: 2687215 Forward-Port-Of: odoo/enterprise#22509 Forward-Port-Of: odoo/enterprise#22216
A typo causing an error in the rule 'Expat End of Service Benefit'. The rule 'Social Insurance Contribution' was in the category deduction but that causes it to be removed from net salary. It is now in the category 'company contribution'. Remove the no update to allow easy update in the future in case of changes (like a law change) Forward-Port-Of: odoo/enterprise#22513
Original PR description
A typo causing an error in the rule 'Expat End of Service Benefit'. The rule 'Social Insurance Contribution' was in the category deduction but that causes it to be removed from net salary. It is now in the category 'company contribution'. Remove the no update to allow easy update in the future in case of changes (like a law change) Forward-Port-Of: odoo/enterprise#22513
Forward-Port-Of: odoo/enterprise#22469
Original PR description
Forward-Port-Of: odoo/enterprise#22469
Adapt tour triggers to avoid unwanted race conditions. Scanning the last product of a picking then checking the Validate button could be done so quickly the button is not yet highlighted. Forward-Port-Of: odoo/enterprise#22481
Original PR description
Adapt tour triggers to avoid unwanted race conditions. Scanning the last product of a picking then checking the Validate button could be done so quickly the button is not yet highlighted. Forward-Port-Of: odoo/enterprise#22481