Thursday, September 30, 2021
42 changes · master
Enhancements to existing features
The calendar appointment backend no longer shows the preset option to group appointments by availability. This simplifies the interface by removing a grouping choice that was not very useful, while users can still create a custom availability grouping if needed.
Original PR description
This commit will apply a minor change on the appointment module: It will remove the preset that allow the user to group the appointments by availability (in the backend). task-2646322 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The email composer and email/SMS resend windows have been redesigned with clearer labels, guidance text, and more relevant action buttons. This makes it easier for users to understand sending options, handle failed messages, and avoid confusing actions such as creating records from failure views.
Original PR description
This merge will improve the layout of the mail composer and the resend modals
* revamp the mail composer and the resend modals: It will update the labels,
clarify the helper messages and make the buttons more dynamic;
* simplify the mail composer: advanced options will be placed in a dedicated
pane;
* various minor layout adjustments;
See commit messages for more info.
Task-2523036Delivery records now include editable shipment descriptions and declared values. This helps businesses provide more accurate customs information and include shipping costs in declared shipment values.
Original PR description
In this commit: =========================== Added two new fields in stock picking related to shipping 1. shipment_description 2. shipment_declared_value Before this commit: ========================= The value of shipment description was static `MY DESCRIPTION` which might be rejected by customs so we added field to set the description value default by taking the category name of the first product from the sale order line. The value of declared value was the total amount of movelines which was not including shipping cost so in this commit we set the value of declared field to total amount of sales order. task-id: 2611210 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Payment creation and registration now only shows journals that have suitable payment methods available. This reduces confusion for users and helps prevent choosing journals that cannot process the payment.
Original PR description
When registering/creating payments, filter out from the selection the journals that do not have any relevant payment method lines. Also, always show payment method lines even when there are only one of them. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The appointment listing page now uses a clearer browser tab title, making it easier for users to understand they are viewing appointment types. Backend reporting also gains a preset to group online appointments by type, helping teams analyze appointment activity more quickly.
Original PR description
This commit will apply minor changes on the appointment module: It will: - Update the page title of the appointment listing layout (in the frontend). - Add a new preset to group the appointments by type (in the backend). task-2646322 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Removed unnecessary styling from the gift card point-of-sale area that was causing popups to behave incorrectly. This helps ensure gift card-related popups display and function more reliably for users.
Original PR description
Remove useless CSS that lead to wrong behavior with popups. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Forward-Port-Of: odoo/odoo#77401
Original PR description
Forward-Port-Of: odoo/odoo#77401
Forward-Port-Of: odoo/odoo#77305
Original PR description
Forward-Port-Of: odoo/odoo#77305
Forward-Port-Of: odoo/odoo#77337
Original PR description
Forward-Port-Of: odoo/odoo#77337
In some cases, it is impossible to validate some landed costs ("Cost and adjustments lines do not match.[...]") To reproduce the issue: (Enable debug mode) 1. Set the Decimal Accuracy of Product Price to 4 2. Create a Product Category PC: - Costing Method: FIFO 3. Create 4 storable products (category PC) 4. Create a service product (landed cost) 5. Create a PO with the 4 products: - 6 x $0.92 - 6 x $0.92 - 3 x $75.17 - 6 x $20.54 6. Process the delivery D 7.
Original PR description
In some cases, it is impossible to validate some landed costs ("Cost and adjustments lines do not match.[...]") To reproduce the issue: (Enable debug mode) 1. Set the Decimal Accuracy of Product…
In some cases, it is impossible to validate some landed costs ("Cost and
adjustments lines do not match.[...]")
To reproduce the issue:
(Enable debug mode)
1. Set the Decimal Accuracy of Product Price to 4
2. Create a Product Category PC:
- Costing Method: FIFO
3. Create 4 storable products (category PC)
4. Create a service product (landed cost)
5. Create a PO with the 4 products:
- 6 x $0.92
- 6 x $0.92
- 3 x $75.17
- 6 x $20.54
6. Process the delivery D
7. Create a Landed Cost:
- Delivery: D
- Product: the service product
- Split Method: By Quantity
- Cost: $1000
8. Compute the landed costs + Validate
Error: a User Error is raised "Cost and adjustments lines do not match.
You should maybe recompute the landed costs.". The sum of the additional
landed cost equals $999.99 instead of $1000
From version 14, `additional_landed_cost` is a Monetary field and its
rounding property is no more based on "Product Price":
https://github.com/odoo/odoo/blob/800433bde03a36ead40a78bc6d53cbb95c24f97b/addons/stock_landed_costs/models/stock_landed_cost.py#L371-L372
Therefore, we should use the rounding of the associated currency to
round its value
OPW-2637701
OPW-2631718
OPW-2649348
Forward-Port-Of: odoo/odoo#77155Steps: - Create Repair with Customer - Send Quotation Issue: - As we don't have `partner_id` on repair, It is displaying `False`. 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#77196
Original PR description
Steps: - Create Repair with Customer - Send Quotation Issue: - As we don't have `partner_id` on repair, It is displaying `False`. 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#77196
BEFORE THIS COMMIT / How to reproduce : Consider a multiple choice question with single answer. A. 2 points B. 1 point C. -1 point Here, the user can only select one answer. He picks A. He only obtains 2/3 points. This is because the maximum score was computed as the sum of all positive scores for the question. It does not make sense, as the student can only pick one answer. Therefore, the formula does not allow giving partial scores (here, answer B, close to the correct answer) w
Original PR description
BEFORE THIS COMMIT / How to reproduce : Consider a multiple choice question with single answer. A. 2 points B. 1 point C. -1 point Here, the user can only select one answer. He picks A. He only…
BEFORE THIS COMMIT / How to reproduce : Consider a multiple choice question with single answer. A. 2 points B. 1 point C. -1 point Here, the user can only select one answer. He picks A. He only obtains 2/3 points. This is because the maximum score was computed as the sum of all positive scores for the question. It does not make sense, as the student can only pick one answer. Therefore, the formula does not allow giving partial scores (here, answer B, close to the correct answer) while maintaining correct score percentages. AFTER THIS COMMIT: The sum of positive scores is still used as maximum score for multiple choice with multiple answers, as we want the student to pick all good answers for max score. However, for multiple choice with single answer, we use the maximum positive score (or 0, if none) among answers, as it the maximum score one can get while selecting a single answer. -> example above : I pick A, I obtain 2 points out of max(2, 1, (0)) = 2 -> I obtain max score for the question. 2/2. ps: As the sum only uses striclty positive values, the negative points are still operational and the flow is not changed. TESTS: A test test_partial_scores_simple_choice is added to make sure the simple_choice is repaired and always gives 100% of points if the best answer is picked. Task-Id - 2533836 Forward-Port-Of: odoo/odoo#76326
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#77318
Original PR description
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#77318
This PR introduces a new component: the layout component. Its purpose is to make abstraction of most generic components and classes when writing a view template or an action. To make use of this component, we also needed a new system to pass slot from the parent of the layout to the control panel. This was done in a hacky way and is meant to be replaced as soon as Owl provides a built-in way to pass slots. The control panel has also been slightly tweaked to default its props from an
Original PR description
This PR introduces a new component: the layout component. Its purpose is to make abstraction of most generic components and classes when writing a view template or an action. To make use of this component, we also needed a new system to pass slot from the parent of the layout to the control panel. This was done in a hacky way and is meant to be replaced as soon as Owl provides a built-in way to pass slots. The control panel has also been slightly tweaked to default its props from an environment's newly introduced key: the 'config'. This has been done to reduce the amount of props passed to the layout and search subcomponents. Forward-Port-Of: odoo/odoo#76140
Customisations made by the themes for the Text-Block snippet were also applied in the Tabs snippet. And so, options like paddings and background-color generated unexpected and potentially broken layouts. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#77391
Original PR description
Customisations made by the themes for the Text-Block snippet were also applied in the Tabs snippet. And so, options like paddings and background-color generated unexpected and potentially broken layouts. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#77391
Instead of the delete icon next to the operations in a BoM, create a button to archive the operation. Archiving an operation will also archive the corresponding Quality Check. Task-ID: 2619450 Enterprise-PR: https://github.com/odoo/enterprise/pull/20785 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76376
Original PR description
Instead of the delete icon next to the operations in a BoM, create a button to archive the operation. Archiving an operation will also archive the corresponding Quality Check. Task-ID: 2619450 Enterprise-PR: https://github.com/odoo/enterprise/pull/20785 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76376
ISSUE: The click on "THEME" tab in editor panel triggers the '_onThemeTabClick' method which: 1- Starts the loader ('_execWithLoadingEffect' method). 2- Runs '_activateSnippet' which uses the same mutex as the loader. Execution order: A1- '_execWithLoadingEffect' with promise: adds the loader in the DOM immediately. A2- '_activateSnippet' sets a second loader to be added after a delay = 500. A3- 'releaseLoader' removes the first loader. A4- '_activateSnippet' ends : (before a
Original PR description
ISSUE: The click on "THEME" tab in editor panel triggers the '_onThemeTabClick' method which: 1- Starts the loader ('_execWithLoadingEffect' method). 2- Runs '_activateSnippet' which uses the same…
ISSUE:
The click on "THEME" tab in editor panel triggers the
'_onThemeTabClick' method which:
1- Starts the loader ('_execWithLoadingEffect' method).
2- Runs '_activateSnippet' which uses the same mutex as the
loader.
Execution order:
A1- '_execWithLoadingEffect' with promise: adds the loader in
the DOM immediately.
A2- '_activateSnippet' sets a second loader to be added after
a delay = 500.
A3- 'releaseLoader' removes the first loader.
A4- '_activateSnippet' ends : (before adding the second
loader: t(4) - t(2) < 500) and timeout is cleared.
In some cases we get t(4) - t(2) > 500 which adds a second
loader to the DOM, and the new flow will be:
B1- Same as A1.
B2- Same as A2.
B3- Second loader added to the DOM / replaces the first one
in 'loadingElements'.
B4- 'releaseLoader' removes the second loader (from the DOM
& 'this.loadingElements').
B5- Same as A4 but the first loader still in the DOM.
The goal of this commit is to fix this behaviour by preventing
more than one loader on the target element.
task-2656308
Forward-Port-Of: odoo/odoo#77424
Forward-Port-Of: odoo/odoo#77226Since [1], a footer effect option has been introduced which allows to have the content hovering the footer to then reveal it when reaching the bottom of the page (instead of having the footer to scroll like the rest of the content). To achieve that, the body color was forced on the snippet container (the `<main/>`) so that the transparent snippet still appear with a background color for the time they go over the footer. That background color should however not have been forced in non-fu
Original PR description
Since [1], a footer effect option has been introduced which allows to have the content hovering the footer to then reveal it when reaching the bottom of the page (instead of having the footer to scroll like the rest of the content). To achieve that, the body color was forced on the snippet container (the `<main/>`) so that the transparent snippet still appear with a background color for the time they go over the footer. That background color should however not have been forced in non-full layouts as another is already forced in that case. In those non-full layout, the "full" body background (= background of color combination 1) is applied on the snippet container but the "body" color is another color which is customizable by the user too. [1]: https://github.com/odoo/odoo/commit/5879e40445f0176d545b4a50f7f7ec33b2e171c8 Related to task-2590182 Forward-Port-Of: odoo/odoo#77490
The empty string, the forward slash `/` and NULL are all to be considered as without a sequence set on `account.move`. While this is just true, it was detected because of non deterministic bugs at the end of the month because the tax closing move was explicitly set to an empty string on version 14.3 and higher. See: https://github.com/odoo/enterprise/commit/4641825daa0ed3b8e407fb3817c582cb541e88a4 Most of the tests posting an entry in the MISC journal could then randomly fail on the las
Original PR description
The empty string, the forward slash `/` and NULL are all to be considered as without a sequence set on `account.move`. While this is just true, it was detected because of non deterministic bugs at the end of the month because the tax closing move was explicitly set to an empty string on version 14.3 and higher. See: https://github.com/odoo/enterprise/commit/4641825daa0ed3b8e407fb3817c582cb541e88a4 Most of the tests posting an entry in the MISC journal could then randomly fail on the last day of the month.git -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#77481
This commit will merge welcome and thread views in the same route and template. The aim is to make the user interacting with the page (by landing them on the welcome view first) so that the browser allows the page to play audio and to switch to full screen. Forward-Port-Of: odoo/odoo#77070
Original PR description
This commit will merge welcome and thread views in the same route and template. The aim is to make the user interacting with the page (by landing them on the welcome view first) so that the browser allows the page to play audio and to switch to full screen. Forward-Port-Of: odoo/odoo#77070
In some contexts, an error caught by the error service has no stack, trying to annotate the stacktrace of this error with the Stacktrace library crashes, masking the original error which is unwanted. Forward-Port-Of: odoo/odoo#77397
Original PR description
In some contexts, an error caught by the error service has no stack, trying to annotate the stacktrace of this error with the Stacktrace library crashes, masking the original error which is unwanted. Forward-Port-Of: odoo/odoo#77397
The message 'Don't worry, you can switch later' is displayed in the breadcrumb of the theme kanban view. When we reach this kanban view from the website settings we want to hide this message. task-2610896 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#76886
Original PR description
The message 'Don't worry, you can switch later' is displayed in the breadcrumb of the theme kanban view. When we reach this kanban view from the website settings we want to hide this message. task-2610896 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#76886
Previously the configurator retrieved the snippet lists needed to build the website pages from IAP. These lists have been put in the theme manifests and can be accessed from it. 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#77243
Original PR description
Previously the configurator retrieved the snippet lists needed to build the website pages from IAP. These lists have been put in the theme manifests and can be accessed from it. 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#77243
Problem: When installing the Austrian localisation no demo company is created. Solution: Create demo_company.xml and add it to the manifest task: 2631136 Forward-Port-Of: odoo/odoo#77420
Original PR description
Problem: When installing the Austrian localisation no demo company is created. Solution: Create demo_company.xml and add it to the manifest task: 2631136 Forward-Port-Of: odoo/odoo#77420
Forward-Port-Of: odoo/odoo#77422
Original PR description
Forward-Port-Of: odoo/odoo#77422
Since https://github.com/odoo/odoo/pull/69124,the UBL template is wrong because of the order of the elements in `PaymentMeans` because it is a sequence `PaymentDueDate` must be in second position (before `InstructionId`) https://www.w3schools.com/xml/el_sequence.asp https://docs.oasis-open.org/ubl/prd1-UBL-2.1/xsd/common/UBL-CommonAggregateComponents-2.1.xsd see `<xsd: complexType name = "PaymentMeansType">` OPW-2468492 Forward-Port-Of: odoo/odoo#77443 Forward-Port-Of: odoo/odoo#77317
Original PR description
Since https://github.com/odoo/odoo/pull/69124,the UBL template is wrong because of the order of the elements in `PaymentMeans` because it is a sequence `PaymentDueDate` must be in second position (before `InstructionId`) https://www.w3schools.com/xml/el_sequence.asp https://docs.oasis-open.org/ubl/prd1-UBL-2.1/xsd/common/UBL-CommonAggregateComponents-2.1.xsd see `<xsd: complexType name = "PaymentMeansType">` OPW-2468492 Forward-Port-Of: odoo/odoo#77443 Forward-Port-Of: odoo/odoo#77317
Forward-Port-Of: odoo/odoo#77469
Original PR description
Forward-Port-Of: odoo/odoo#77469
When adding an odd width images on website, a thin black line is drawn on its right side. The problem comes from the getSourceCanvas of the cropperjs library. A translation is applied followed by an other translation in the opposite direction. However the second translation was not the exact reverse of the first due to a rounding problem. The fix proposed here comes from: https://github.com/fengyuanchen/cropperjs/pull/300/commits/a6481c052cfc93ef14dd95a3bd00142215dda36e task-2652904
Original PR description
When adding an odd width images on website, a thin black line is drawn on its right side. The problem comes from the getSourceCanvas of the cropperjs library. A translation is applied followed by an other translation in the opposite direction. However the second translation was not the exact reverse of the first due to a rounding problem. The fix proposed here comes from: https://github.com/fengyuanchen/cropperjs/pull/300/commits/a6481c052cfc93ef14dd95a3bd00142215dda36e task-2652904 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#77039
Before this commit, a user could DM a portal user. Portal user are not supported and can't chat. task-2632874 Forward-Port-Of: odoo/odoo#77489
Original PR description
Before this commit, a user could DM a portal user. Portal user are not supported and can't chat. task-2632874 Forward-Port-Of: odoo/odoo#77489
-- This is a follow-up of odoo/odoo#72736 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to filter on dates, SOs or Field Service projects. Improving this is very difficult and would require weeks of development that are not worth it. In any case, all the information provided by the project overview can be found elsewhere. The stat buttons of the report are basically duplicates of the on
Original PR description
-- This is a follow-up of odoo/odoo#72736 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to filter on…
-- This is a follow-up of odoo/odoo#72736 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to filter on dates, SOs or Field Service projects. Improving this is very difficult and would require weeks of development that are not worth it. In any case, all the information provided by the project overview can be found elsewhere. The stat buttons of the report are basically duplicates of the ones from the project form view. Therefore, we are removing this report and its twin, the Project Costs and Revenues. In addition, analytic items lack context for the user to understand what generated a certain cost or revenue: there is no link to the source document; the entries are not categorized (e.g. it is not easy to understand if a cost comes from a timesheet cost, a purchase order or an expense); the billable type group by works fine for timesheets but then all the other entries are flagged as Undefined, which is not very helpful; there is no option to easily isolate costs from revenues. task-2637495 See odoo/enterprise#20740 Forward-Port-Of: odoo/odoo#76247
Since https://github.com/odoo/enterprise/pull/19531 The filter was wrong because the two conditions (sql request server-side and of the bills to pay filter) are not the same. https://github.com/odoo/enterprise/blob/fdad6a7d1411a6f1f3685d6b40e2a81f30682b0c/account_3way_match/views/account_invoice_view.xml#L28 https://github.com/odoo/enterprise/blob/55998d8a05ae7c4d0eaee0b47874efa184a902f1/account_3way_match/models/account_journal_dashboard.py#L28 This means that we can have cases where:
Original PR description
Since https://github.com/odoo/enterprise/pull/19531 The filter was wrong because the two conditions (sql request server-side and of the bills to pay filter) are not the same. https://github.com/odoo/enterprise/blob/fdad6a7d1411a6f1f3685d6b40e2a81f30682b0c/account_3way_match/views/account_invoice_view.xml#L28 https://github.com/odoo/enterprise/blob/55998d8a05ae7c4d0eaee0b47874efa184a902f1/account_3way_match/models/account_journal_dashboard.py#L28 This means that we can have cases where: It is displayed in the dashboard: 1 Bill To Pay But once we click on it, the Bill To Pay filter doesn't show us any records It can happen when the due date is equal to today. OPW-2513075 Forward-Port-Of: odoo/enterprise#21232
-- This is a follow up of odoo/enterprise#19250 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to filter on dates, SOs or Field Service projects. Improving this is very difficult and would require weeks of development that are not worth it. In any case, all the information provided by the project overview can be found elsewhere. The stat buttons of the report are basically duplicates of
Original PR description
-- This is a follow up of odoo/enterprise#19250 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to…
-- This is a follow up of odoo/enterprise#19250 -- The project overview is a significant technical debt as it is a custom qweb view. It is quite limited: It is not possible to group the data, to filter on dates, SOs or Field Service projects. Improving this is very difficult and would require weeks of development that are not worth it. In any case, all the information provided by the project overview can be found elsewhere. The stat buttons of the report are basically duplicates of the ones from the project form view. Therefore, we are removing this report and its twin, the Project Costs and Revenues. In addition, analytic items lack context for the user to understand what generated a certain cost or revenue: there is no link to the source document; the entries are not categorized (e.g. it is not easy to understand if a cost comes from a timesheet cost, a purchase order or an expense); the billable type group by works fine for timesheets but then all the other entries are flagged as Undefined, which is not very helpful; there is no option to easily isolate costs from revenues. task-2637495 See odoo/odoo#76247 Forward-Port-Of: odoo/enterprise#20740
…enamed - open a spreadsheet - rename the spreadsheet - right click on a pivot formula => "See records" => the spreadsheet name in the breadcrumb is the previous name Forward-Port-Of: odoo/enterprise#21303
Original PR description
…enamed - open a spreadsheet - rename the spreadsheet - right click on a pivot formula => "See records" => the spreadsheet name in the breadcrumb is the previous name Forward-Port-Of: odoo/enterprise#21303
Have an account [DEF] for deferred revenue with: - Type: 'Current Liabilities' - Automate Deferred Revenue: no Create an invoice, add on the line a product and change the account to [DEF], confirm. Create a deferred revenue: - recalling the created invoice. - Number of recognitions 12 Months - For test purposes set the first recognition date in the past (at the beginning of the year) so to have already some posted entries - Revenue Account: Current Assets - Deferred revenue account:
Original PR description
Have an account [DEF] for deferred revenue with: - Type: 'Current Liabilities' - Automate Deferred Revenue: no Create an invoice, add on the line a product and change the account to [DEF], confirm. Create a deferred revenue: - recalling the created invoice. - Number of recognitions 12 Months - For test purposes set the first recognition date in the past (at the beginning of the year) so to have already some posted entries - Revenue Account: Current Assets - Deferred revenue account: [DEF] - Journal: Misc Confirm the deferred revenue, entries will be created, some of them already posted The residual amount to recognize will be the original value of the asset, not taking into account the posted entries opw-2612578 Forward-Port-Of: odoo/enterprise#21238
The sequence value for draft moves should be '/' so that we can see it in the list view, and so that 'Draft' is displayed in the form view, and that the name is not editable before posting it for the first time. Forward-Port-Of: odoo/enterprise#21304
Original PR description
The sequence value for draft moves should be '/' so that we can see it in the list view, and so that 'Draft' is displayed in the form view, and that the name is not editable before posting it for the first time. Forward-Port-Of: odoo/enterprise#21304
This test is a followup to odoo/enterprise#21157 Adds a test to make sure that final_yearly_costs never changes, or at least stay within margin of error, upon modifying 'sacrifical advantages' (extra time off, insurance groups). TaskId-2655785 Forward-Port-Of: odoo/enterprise#21298
Original PR description
This test is a followup to odoo/enterprise#21157 Adds a test to make sure that final_yearly_costs never changes, or at least stay within margin of error, upon modifying 'sacrifical advantages' (extra time off, insurance groups). TaskId-2655785 Forward-Port-Of: odoo/enterprise#21298
Instead of the delete icon next to the operations in a BoM, create a button to archive the operation. Archiving an operation will also archive the corresponding Quality Check. When a user finishes an operation containing several steps, removes the breadcrumbs of the page obtained after. Task-ID: 2619450 Community-PR: https://github.com/odoo/odoo/pull/76376 Forward-Port-Of: odoo/enterprise#20785
Original PR description
Instead of the delete icon next to the operations in a BoM, create a button to archive the operation. Archiving an operation will also archive the corresponding Quality Check. When a user finishes an operation containing several steps, removes the breadcrumbs of the page obtained after. Task-ID: 2619450 Community-PR: https://github.com/odoo/odoo/pull/76376 Forward-Port-Of: odoo/enterprise#20785
Steps to reproduce the bug: - create a vendor bill for product X (use whatever as long as it's not archived) - remember what's in the label field of the bill line (usually the name of the product) - validate the vendor bill - archive X - create a new vendor bill and add a line - in the label field, add whatever word that appeared in the label of the previous bill - clic outside Bug: The archived product X was suggested. opw:2513816 Forward-Port-Of: odoo/enterprise#20958
Original PR description
Steps to reproduce the bug: - create a vendor bill for product X (use whatever as long as it's not archived) - remember what's in the label field of the bill line (usually the name of the product) - validate the vendor bill - archive X - create a new vendor bill and add a line - in the label field, add whatever word that appeared in the label of the previous bill - clic outside Bug: The archived product X was suggested. opw:2513816 Forward-Port-Of: odoo/enterprise#20958
Forward-Port-Of: odoo/enterprise#21261
Original PR description
Forward-Port-Of: odoo/enterprise#21261
This PR is the counter part of https://github.com/odoo/odoo/pull/76140 Forward-Port-Of: odoo/enterprise#20683
Original PR description
This PR is the counter part of https://github.com/odoo/odoo/pull/76140 Forward-Port-Of: odoo/enterprise#20683
…r tests This commit simplifies the social_push_notifications "test_post" to remove the need for the firebase_admin package. This should have been done during 6624e637ce438860326b033e4a25fdb718d84b8e (You can find more information about why we removed firebase_admin on the commit here above). Mocking the "_firebase_send_message_from_configuration" method in the test works for all cases. Meaning the test should always pass from now on regardless of the existence of the firebase_adm
Original PR description
…r tests This commit simplifies the social_push_notifications "test_post" to remove the need for the firebase_admin package. This should have been done during 6624e637ce438860326b033e4a25fdb718d84b8e (You can find more information about why we removed firebase_admin on the commit here above). Mocking the "_firebase_send_message_from_configuration" method in the test works for all cases. Meaning the test should always pass from now on regardless of the existence of the firebase_admin package on the running system. The previous mocking was overly complicated and unnecessary anyway since it just returned empty "messaging.SendResponse" elements. Task-2580462 Forward-Port-Of: odoo/enterprise#21268